Closed Bug 306505 Opened 19 years ago Closed 19 years ago

&not in URL causes misinterpretation (not sign)

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: firefox.bugzilla, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)

When the name of a name/value pair in a url is 'not' and it comes after another
name/val pair, the concatenating ampersand causes the name 'not' to be
interpreted as &not, or the not sign logical symbol.

This is important because most webservers will not decode a ¬ to mean &not, and
the proper data won't be passed to the web application.

Reproducible: Always

Steps to Reproduce:
<html><a href="http://www.example.com/index.php?find=string&not=string2">click
here</a></html>



Actual Results:  
part of the data is left out and not passed to index.php

Expected Results:  
php should find that find=string and that not=string2
you need to encode the ampersand as &amp; (you should always do this, not just
for cases that cause a problem)

Marking invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.