Seriously, seems to act really weird.
As a piece of text, it is perfectly valid. However, in a web page, as a "non-standard" character, I convert it from & into & as I am supposed to.
So...
Internal to a database I have a category "Buns & Baps". I decide to convert the "&" into "&" and put that instead.
I'd expect when I post a link with "index.php?category=Buns&Baps" for it to return a value of "Buns%20&%20Baps" for the value of category, however, it seems that the standard behaviour for a browser is to parse the & into a & and then not do the reverse when passing it back, which means that "Baps" is converted into a new variable instead of the end of the first...
Why?? And how can you post "Buns & Baps" as a GET post index.php?category=Buns & Baps (obviously space will be replaced by %20).
EDIT : And just seen, even if using & it will STILL fail and become parsed as a new variable... just nuts.
EDIT : Sorry, my own stupid fault, should have checked up on standards for URLS (http://www.rfc-editor.org/rfc/rfc1738.txt) and HTML (http://www.blooberry.com/indexdot/html/tagpages/text.htm).
Simply converted the URL links to use hex codes to solve.
As a piece of text, it is perfectly valid. However, in a web page, as a "non-standard" character, I convert it from & into & as I am supposed to.
So...
Internal to a database I have a category "Buns & Baps". I decide to convert the "&" into "&" and put that instead.
I'd expect when I post a link with "index.php?category=Buns&Baps" for it to return a value of "Buns%20&%20Baps" for the value of category, however, it seems that the standard behaviour for a browser is to parse the & into a & and then not do the reverse when passing it back, which means that "Baps" is converted into a new variable instead of the end of the first...
Why?? And how can you post "Buns & Baps" as a GET post index.php?category=Buns & Baps (obviously space will be replaced by %20).
EDIT : And just seen, even if using & it will STILL fail and become parsed as a new variable... just nuts.
EDIT : Sorry, my own stupid fault, should have checked up on standards for URLS (http://www.rfc-editor.org/rfc/rfc1738.txt) and HTML (http://www.blooberry.com/indexdot/html/tagpages/text.htm).
Simply converted the URL links to use hex codes to solve.
Last edited: