It's best to assume browsers don't do the right thing in 100% of cases. (Been there, done that with Squid..)
Adrian On Thu, Jan 13, 2011, Trong Long Dinh wrote: > I haven't read RFC 3986. Maybe | _is_ an invalid URI character. But what > happen when i want pass a param contain '|' character. If it's a special > character, then firefox have to encode it before send to server. > > On Thu, Jan 13, 2011 at 11:08 AM, Nick Mathewson <[email protected]>wrote: > > > On Wed, Jan 12, 2011 at 10:51 PM, Trong Long Dinh > > <[email protected]> wrote: > > > I already review source code of libevent. Ur small code has same mean > > with > > > mine. However, Both are meaningless because function static char * > > > end_of_path(char *cp, int allow_qchars) not allow '|' character. If uri > > > query contain '|' character then it response "bad request". > > > > Weird. According to RFC 3986, I think that | _is_ an invalid URI > > character. Ugh. Is there some other standard that specifies how an > > HTTP URI looks that I should be looking at, or is your browser > > expecting servers to handle nonconformant URIs? > > > > -- > > Nick > > *********************************************************************** > > To unsubscribe, send an e-mail to [email protected] with > > unsubscribe libevent-users in the body. > > -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $24/pm+GST entry-level VPSes w/ capped bandwidth charges available in WA - *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe libevent-users in the body.
