Wiadomość napisana w dniu 2008-09-18, o godz. 13:47, przez Graham Dumpleton:
>>>> I saw actual request bodies larger than declared in content-lentgh >>>> with Firefox 2, this browser often was lying to my nginx in cases >>>> of >>>> small bodies by 1-4 bytes. >> >>> What sort of application was that? Were the POSTs in the case >>> actually >>> being generated by AJAX code running in browser? >> >>> I would trust Firefox to be doing the correct thing for basic >>> concepts >>> of HTML form posting and file upload, but I wouldn't be surprised if >>> server provided AJAX code screwed up if there were generating the >>> content length themselves. >> >>> Another possibility is that people were uploading files that were >>> still being written to by some application and thus were changing in >>> length. >> >> Right, these were POST requests made by some ajax. > > BTW, I'd also be a bit suspect on nginx behaviour if it was even > passing through more than Conent-Length. If you were using Apache it > would outright refuse to pass on more content than that specified by > the Content-Length as it trusts that value as being the actual content > length. It has to do that for HTTP/1.1 pipelining to work properly. The body was truncated by nginx to the length declared by browser, so I think nginx was behaving properly. Received data did not show any signs of truncation, thats why I was blaming browser for wrong calculation of content length. -- We read Knuth so you don't have to. - Tim Peters Jarek Zgoda, R&D, Redefine [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
