3 ms·
A quick look at the W3C source on the matter only mentions & as a separator, so I think it's correct to say allowing something else is non-standard. https://ww
by dmurray 5y ago
A quick look at the W3C source on the matter only mentions & as a separator, so I think it's correct to say allowing something else is non-standard.
https://www.w3.org/TR/REC-html40/interact/forms.html#form-content-type https://www.w3.org/TR/REC-html40/interact/forms.html#form-co...
- oblvious-earth 5y ago";" is mentioned in the appendix as an implementation side note: https://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2 https://www.w3.org/TR/1999/REC-html401-19991224/appendix/not...
- tyingq 5y agoThat's the old 1999 spec. You would want the newer, 2014 one: https://www.w3.org/TR/2014/REC-html5-20141028/forms.html#url-encoded-form-data https://www.w3.org/TR/2014/REC-html5-20141028/forms.html#url...
- btilly 5y agoBut at the time that urllib.parse was written, that 1999 spec WAS the official spec.
- jbverschoor 5y ago> We recommend that HTTP server implementors, and in particular, CGI implementors support the use of ";" in place of "&" to save authors the trouble of escaping "&" characters in this manner. Thankfully that did not happen (widespread), and now people understand they have to escape. I do remember jsessionid being after the semi-colon..