Re: Raw HTTP request processing?

Thanks but it seems that in this example (if I have understood correctly) it loads the entire request into memory. I need to convert stuff on the fly using streams on both input and output as both may be huge. I have a number of stages of transformation and it wouldn't take very many requests to

Re: Raw HTTP request processing?

Here's an example: http://www.djangosnippets.org/snippets/1322/ On Aug 25, 5:43 pm, John wrote: > > Isn't it just > > request.raw_post_data > > Thanks and I suspected it was that but hoped there might be a little > example somewhere as the docs don't say much only this: > >

Re: Raw HTTP request processing?

> Isn't it just > request.raw_post_data Thanks and I suspected it was that but hoped there might be a little example somewhere as the docs don't say much only this: HttpRequest.raw_post_data The raw HTTP POST data. This is only useful for advanced processing. Use POST instead. As I am

Re: Raw HTTP request processing?

On Aug 25, 4:54 pm, John Baker wrote: > Some of my views need to process arbitrary incoming data that isn't a > normal web request i.e. process an incoming document and return an > altered document. > > How do I get a view to process raw incoming data rather than the usual

Raw HTTP request processing?

Some of my views need to process arbitrary incoming data that isn't a normal web request i.e. process an incoming document and return an altered document. How do I get a view to process raw incoming data rather than the usual encoded parameters and form etc? It is obvious how to do this on