We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The crawler may still generate URLs like this:
https://taget/script?pageId=327683&selectedPageVersions=58&selectedPageVersions=57&selectedPageVersions=56&selectedPageVersions=55&selectedPageVersions=54&selectedPageVersions=53&selectedPageVersions=50&selectedPageVersions=49&selectedPageVersions=48&selectedPageVersions=47&selectedPageVersions=46&selectedPageVersions=45&selectedPageVersions=44&selectedPageVersions=43&selectedPageVersions=42&--- snip ---&selectedPageVersions=6&selectedPageVersions=5&selectedPageVersions=4&selectedPageVersions=3&selectedPageVersions=2&selectedPageVersions=1
Obviously the cause must be scripts doing stuff like
echo '<a href="'.$url.'&selectedPageVersions='.str($version-1).'">link</a>'
I thought that kind of problem was already fixed. We sould make sure such behavior doesn't happen with GET and POST parameters
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The crawler may still generate URLs like this:
https://taget/script?pageId=327683&selectedPageVersions=58&selectedPageVersions=57&selectedPageVersions=56&selectedPageVersions=55&selectedPageVersions=54&selectedPageVersions=53&selectedPageVersions=50&selectedPageVersions=49&selectedPageVersions=48&selectedPageVersions=47&selectedPageVersions=46&selectedPageVersions=45&selectedPageVersions=44&selectedPageVersions=43&selectedPageVersions=42&--- snip ---&selectedPageVersions=6&selectedPageVersions=5&selectedPageVersions=4&selectedPageVersions=3&selectedPageVersions=2&selectedPageVersions=1
Obviously the cause must be scripts doing stuff like
I thought that kind of problem was already fixed. We sould make sure such behavior doesn't happen with GET and POST parameters
The text was updated successfully, but these errors were encountered: