[tor-talk] .onion eat http 413 errors
Chelsea Komlo
chelsea.komlo at gmail.com
Sun Jul 8 13:14:49 UTC 2018
Hi,
Do you mind confirming that you also have this issue when using the .onion
address to post small amounts of data (as opposed to the large post you
reference in your email)?
If there are any relevant logs from your webserver or the tor deamon that
is serving the onion service, please include those here. It would be
especially useful to know if the request actually is handled by the
webserver.
Thanks,
Chelsea
On Tue, Jul 3, 2018 at 5:45 AM, Nirgal <contact_tor at nirgal.com> wrote:
> Hi
>
> I am working on a web site that allow users to post big files.
>
> Because some people don't use javascript, and because I don't want to use
> the
> PHP limit where an error message such as "Sorry uploads are limited to
> 1MB"
> appears *after* the user spent many hours uploading a 1GB file, I am
> trying to
> use the good old 413 errors generated by apache LimitRequestBody
> directive, or
> simmilar stuff from nginx.
>
> It works ok when I use TorBundle to post on my regular
> https://example.com/
> site. I get my nice HTTP 413 error page with custom explanations.
>
> But when I use the .onion address to do a big post, I always get a generic
> "The connection was reset" message, and no http error code, nor customized
> error message.
> It's a bit like if the browser doesn't even try to read the answer before
> the
> connection with the POST is hang by the server, when the .onion is used.
>
> Did any one already experience that behaviour?
> Any known work around?
> --
> tor-talk mailing list - tor-talk at lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
--
Chelsea H. Komlo
Twitter: @chelseakomlo
More information about the tor-talk
mailing list