-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle old CGI URL path information (by ignoring it) #204
Comments
@[email protected] changed milestone from |
@[email protected] commented Moving this to 2.03 even if I don't think we will have time to handle it -- it's good to see what's on the table. |
@[email protected] changed status from |
@[email protected] changed owner from `` to |
@[email protected] changed status from |
@[email protected] changed resolution from `` to |
@[email protected] commented (In 562819a) Use non-greedy matching to stop at the first ".cgi" in the Fixes #204. |
@[email protected] commented (In 562819a) Use non-greedy matching to stop at the first ".cgi" in the Fixes #204. |
3 similar comments
@[email protected] commented (In 562819a) Use non-greedy matching to stop at the first ".cgi" in the Fixes #204. |
@[email protected] commented (In 562819a) Use non-greedy matching to stop at the first ".cgi" in the Fixes #204. |
@[email protected] commented (In 562819a) Use non-greedy matching to stop at the first ".cgi" in the Fixes #204. |
owner:[email protected]
resolution_fixed
type_defect
| by [email protected]The google webmaster site report shows a lot of 404s of the kind
We don't handle these currently, but for a traditional cgi script the second
/idnindex.cgi
will appear as cgi path information, and be ignored by thelegacy implementation -- so the expected result would be returned.
We should probably handle this by ignoring the path information.
Issue migrated from trac:204 at 2022-03-04 00:47:28 +0000
The text was updated successfully, but these errors were encountered: