On Sat, Nov 1, 2008 at 11:37 AM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> I actually am seeing some input, but it is divided into several, well,
> chunks. I guess it's the same problem as seeing no input - I'd say
> you're right and chunked encoding is silently unsupported (it would be
>
I actually am seeing some input, but it is divided into several, well,
chunks. I guess it's the same problem as seeing no input - I'd say
you're right and chunked encoding is silently unsupported (it would be
nice if Django said something though).
However, could you please suggest any workaround?
On Nov 1, 10:40 am, "Tomáš Brambora" <[EMAIL PROTECTED]> wrote:
> I have a standard Django installation without any changes in the
> settings (except adding mysql db to the settings.py) and I'm sending
> the message to localhost:8000, so there is no proxy or anything else
> in the way. Still, th
I have a standard Django installation without any changes in the
settings (except adding mysql db to the settings.py) and I'm sending
the message to localhost:8000, so there is no proxy or anything else
in the way. Still, the request body comes after me sending the
response...
On Fri, Oct 31, 200
[EMAIL PROTECTED] wrote:
> Hello,
> I'm trying to receive a possibly large XML message via HttpRequest
> (POST method) with chunked encoding. However, when I send a response,
> I found out (using Wireshark) that the response is being sent before
> the whole POST request body is available. I expe
Hello,
I'm trying to receive a possibly large XML message via HttpRequest
(POST method) with chunked encoding. However, when I send a response,
I found out (using Wireshark) that the response is being sent before
the whole POST request body is available. I expected Django to be
buffering the chunk
6 matches
Mail list logo
