# Reverse proxy requires http header from upstream? **URL:** \ **Category:** NGINX\ **Created:** [November 4, 2012, 3:26am UTC](https://www.ruby-forum.com/t/reverse-proxy-requires-http-header-from-upstream/224227 "2012-11-04T03:26:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![aris](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/258eb7/32.png) [@aris](https://www.ruby-forum.com/u/aris)\ **Post date:** [November 4, 2012, 3:26am UTC](https://www.ruby-forum.com/t/reverse-proxy-requires-http-header-from-upstream/224227/1 "2012-11-04T03:26:19Z")
Hi all, I’m trying to use nginx as a reverse proxy for several softwares that comes with webui, e.g. Transmission, MLDonkey, etc. All are working well except for aMule, which I can connect directly to its port, but when I use nginx it always prompts timeout in error log. The major difference between aMule and the rest is that amule web server does not give a http header to the client, for when I try to use curl to grab the header it gives an empty response. (Although it will return the correct webpage when curl grabs the webpage) And I suppose that is the reason nginx thinks connection timeout. So I wonder if there is any way to let nginx “ignore” the http header from the upstream and just pass the data whatever the upstream gives? Thanks in advance. Posted at Nginx Forum: > **[Reverse proxy requires http header from upstream?](https://forum.nginx.org/read.php?2,232492,232492#msg-232492)** > > Hi all, I'm trying to use nginx as a reverse proxy for several softwares that comes with webui, e.g. Transmission, MLDonkey, etc. All are working well except for aMule, which I can connect directly to its port, but when I use nginx it always prompts... ---
**Author:** ![raidenii](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e99b99/32.png) [@raidenii](https://www.ruby-forum.com/u/raidenii)\ **Post date:** [November 4, 2012, 1:28pm UTC](https://www.ruby-forum.com/t/reverse-proxy-requires-http-header-from-upstream/224227/2 "2012-11-04T13:28:40Z")
On 4 November 2012 02:25, raidenii [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > The major difference between aMule and the rest is that amule web server > does not give a http header to the client, for when I try to use curl to > grab the header it gives an empty response. (Although it will return the > correct webpage when curl grabs the webpage) And I suppose that is the > reason nginx thinks connection timeout. > > So I wonder if there is any way to let nginx “ignore” the http header from > the upstream and just pass the data whatever the upstream gives? Thanks in > advance. When you say “http header”, which one do you mean? If you mean _all_ headers are missing, and the server simple responds with data, then the server isn’t actually talking HTTP at all, and nginx is not the right tool for the job. If that’s the case, you should consider load-balancing/reverse-proxying it either with something that does talk the protocol that’s being used, or something generic that can proxy at the TCP layer, like HAProxy. ## Jonathan Jonathan M. // Oxford, London, UK > **[Jonathan Matthews :: Words Typed, Great Rates For Cash](https://www.jpluscplusm.com)** ---
**Author:** ![raidenii](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/e99b99/32.png) [@raidenii](https://www.ruby-forum.com/u/raidenii)\ **Post date:** [November 4, 2012, 2:58pm UTC](https://www.ruby-forum.com/t/reverse-proxy-requires-http-header-from-upstream/224227/3 "2012-11-04T14:58:04Z")
## Jonathan M. Wrote: > > > > nginx is not the right tool for the job. > > * * * > > nginx mailing list > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) > [mailman.nginx.org archive](http://mailman.nginx.org/mailman/listinfo/nginx) I have tried backend upstream+proxy\_pass, but seems not working either. Strangely when using browser to acess directly there is no problem at all. Posted at Nginx Forum: [http://forum.nginx.org/read.php?2,232492,232494#msg-232494](http://forum.nginx.org/read.php?2,232492,232494#msg-232494)