okie, thanks
On Sun, Feb 13, 2011 at 12:48 PM, Nick Mathewson wrote:
> On Thu, Jan 13, 2011 at 12:29 AM, 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
> > characte
On Thu, Jan 13, 2011 at 12:29 AM, 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.
Okay, there's code to t
On Wed, Jan 19, 2011, Nick Mathewson wrote:
> On Thu, Jan 13, 2011 at 12:34 AM, Adrian Chadd wrote:
> > It's best to assume browsers don't do the right thing in 100% of cases.
> >
> > (Been there, done that with Squid..)
>
> Ick. Okay, what does Squid (or some other sensible application)
> assum
On Wed, Jan 19, 2011, Nick Mathewson wrote:
> On Thu, Jan 13, 2011 at 12:34 AM, Adrian Chadd wrote:
> > It's best to assume browsers don't do the right thing in 100% of cases.
> >
> > (Been there, done that with Squid..)
>
> Ick. Okay, what does Squid (or some other sensible application)
> assum
On Thu, Jan 13, 2011 at 12:34 AM, Adrian Chadd wrote:
> It's best to assume browsers don't do the right thing in 100% of cases.
>
> (Been there, done that with Squid..)
Ick. Okay, what does Squid (or some other sensible application)
assume constitutes a valid URI?
(I wonder whether this argues
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
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 wrote:
> On Wed, Jan 12, 2011 at 10:5
On Wed, Jan 12, 2011 at 10:51 PM, Trong Long Dinh
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 '|'
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".
On Thu, Jan 13, 2011
On Wed, Jan 12, 2011 at 6:10 AM, Trong Long Dinh
wrote:
> Hi all.
> I setup a simple httpd like this:
>
>> #include
>> #include
>> #include
>>
>> #include
>> #include
>> #include
>> #include
>>
>> void now_handler(struct evhttp_request *req, void *arg) {
>> struct evbuffer *buf = evhttp
Hi all.
I setup a simple httpd like this:
#include
> #include
> #include
>
> #include
> #include
> #include
> #include
>
> void now_handler(struct evhttp_request *req, void *arg) {
> struct evbuffer *buf = evhttp_request_get_output_buffer(req);
> evbuffer_add_printf(buf, "{\"now\":%
11 matches
Mail list logo