On Sun, Apr 11, 2010 at 2:45 PM, rangeli nepal wrote:
> Just to verify my suspicion about the payload I set the authorization header
> to my name. It works well. I mean it went well fore small pay load.
> However, with the token it determines that it is a bad request before it get
> the full head
Just to verify my suspicion about the payload I set the authorization header
to my name. It works well. I mean it went well fore small pay load.
However, with the token it determines that it is a bad request before it get
the full header.
An example of tcpdump
14:33:57.928844 IP blueye.cis.foo
will %{error-notes}n work on https too. I am asking it as I am getting
following statement in ssl_error.log
[Sun Apr 11 07:34:40 2010] [error] [client 192.168.128.122] request failed:
error reading the headers
[Sun Apr 11 07:34:40 2010] [debug] ssl_engine_kernel.c(1884): OpenSSL:
Write: SSL negoti
On Sat, Apr 10, 2010 at 10:17 PM, rangeli nepal wrote:
> Good Evening Everybody,
> I am trying to send a authorization header where token in pretty big( around
> 2.5 kb).
> It is going in form of
> Authorization: Custom value
> However apache responds me with bad request. looking at the tcpdump I
Good Evening Everybody,
I am trying to send a authorization header where token in pretty big( around
2.5 kb).
It is going in form of
Authorization: Custom value
However apache responds me with bad request. looking at the tcpdump I see
the header spanning in two tcp packets. I was wondering if th
