On Wed, Sep 8, 2010 at 2:38 PM, Nicholas Wehr <[email protected]>wrote:
> interesting problem. so the client is making byte-range requests on dynamic > content? if it's static - I'd recommend you defer this functionality to > apache. > No, it's not that. It's simply that the client is sending a content-length header and after Catalyst / HTTP::Body slurps in the body Catalyst does a sanity check to see if the length of the body really was the length specified in the header. Watch: mose...@bumby2:~$ catalyst.pl Length mose...@bumby2:~$ CATALYST_DEBUG=0 Length/script/length_server.pl You can connect to your server at http://bumby2:3000 mose...@bumby2:~$ telnet localhost 3000 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. POST /foo HTTP/1.1 Host: localhost:3000 Content-Type: application/octet-stream Content-Length: 400000 just some stuff ^] telnet> quit Connection closed. Results in: [error] Caught exception in engine "Wrong Content-Length value: 400000" -- Bill Moseley [email protected]
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
