You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two issues related to the "Create Ticket" button in the Arch Security Tracker.
Issue 1: 414 Request URI Too Long
Steps to Reproduce:
Select an AVG (Average Group Vulnerability).
Click the "Create Ticket" button.
Expected Result:
A new ticket should be created without any errors.
Actual Result:
A 414 Request URI Too Long error is encountered, with the message: "The URI provided was too long for the server to process. Try to make the request URI shorter."
Issue 2: 404 Page Not Found
Steps to Reproduce:
Select an AVG and ensure the URI is shorter than the length that causes the 414 error.
Click the "Create Ticket" button.
Expected Result:
A new ticket should be created without any errors.
Actual Result:
A 404 Page Not Found error is encountered, with the message: "The page you're looking for could not be found. The resource that you are attempting to access does not exist or you don't have the necessary permissions to view it. Make sure the address is correct and that the page hasn't moved. Please contact your GitLab administrator if you think this is a mistake."
The text was updated successfully, but these errors were encountered:
Description
There are two issues related to the "Create Ticket" button in the Arch Security Tracker.
Issue 1: 414 Request URI Too Long
Steps to Reproduce:
Expected Result:
A new ticket should be created without any errors.
Actual Result:
A
414 Request URI Too Long
error is encountered, with the message: "The URI provided was too long for the server to process. Try to make the request URI shorter."Issue 2: 404 Page Not Found
Steps to Reproduce:
Expected Result:
A new ticket should be created without any errors.
Actual Result:
A
404 Page Not Found
error is encountered, with the message: "The page you're looking for could not be found. The resource that you are attempting to access does not exist or you don't have the necessary permissions to view it. Make sure the address is correct and that the page hasn't moved. Please contact your GitLab administrator if you think this is a mistake."The text was updated successfully, but these errors were encountered: