# Nginx proxy vs apache proxy **URL:** \ **Category:** NGINX\ **Created:** [June 5, 2013, 2:40am UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511 "2013-06-05T02:40:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\ **Post date:** [June 5, 2013, 2:40am UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511/1 "2013-06-05T02:40:00Z")
I’m sure this is probably just a misconfiguration or a misunderstanding of nginx proxying. I’m looking to replace apache as my ssl/proxy server for a Jboss/tcServer backend. Unfortunately, I have a java web start app that builds the jnlp files dynamically based on the scheme, protocol and server info passed back to it. I’m not getting the https (port 443) passed back as expected. I thought it was the application so I googled and found a some quick and dirty jsp pages that let me test the responses being passed back. For the apache server, I see the following: Scheme: https Name: [my.example.com](http://my.example.com) Port: 443 Nginx responses show (regardless of how I try to connect): Scheme: http Name: [my.example.com](http://my.example.com) Port: 80 I’m fairly new to nginx but I’ve read and googled fairly extensively to no avail. I’m trying to do similar to the following: ``` location /myJWSapp/ { proxy_pass http://127.0.0.1:8080; proxy_redirect off; proxy_set_header Host ``` $http\_host; proxy\_set\_header X-Forwarded-By $server\_addr:$server\_port; proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for; proxy\_set\_header X-Forwarded-Proto $scheme; } I can see the url in the jnlp file Also, for some reason the jnlp file is now being truncated at 10k (I’ve googled this to no avail as well). This is making it even more difficult to debug this issue. Posted at Nginx Forum: > **[nginx proxy vs apache proxy](https://forum.nginx.org/read.php?2,239872,239872#msg-239872)** > > I'm sure this is probably just a misconfiguration or a misunderstanding of nginx proxying. I'm looking to replace apache as my ssl/proxy server for a Jboss/tcServer backend. Unfortunately, I have a java web start app that builds the jnlp files... ---
**Author:** ![solitaryr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@solitaryr](https://www.ruby-forum.com/u/solitaryr)\ **Post date:** [June 12, 2013, 1:47am UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511/2 "2013-06-12T01:47:04Z")
This apparently handles the proxying differently. Guess it’s back to Apache since it handles it readily and has AJP support. Posted at Nginx Forum: > **[Re: nginx proxy vs apache proxy](https://forum.nginx.org/read.php?2,239872,240043#msg-240043)** > > I'm sure this is probably just a misconfiguration or a misunderstanding of nginx proxying. I'm looking to replace apache as my ssl/proxy server for a Jboss/tcServer backend. Unfortunately, I have a java web start app that builds the jnlp files... ---
**Author:** ![solitaryr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@solitaryr](https://www.ruby-forum.com/u/solitaryr)\ **Post date:** [June 13, 2013, 1:20am UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511/3 "2013-06-13T01:20:42Z")
Hi, > Nginx responses show (regardless of how I try to connect): > > Scheme: http > Name: [my.example.com](http://my.example.com) > Port: 80 > […] > proxy\_set\_header Host $http\_host; > proxy\_set\_header X-Forwarded-By $server\_addr:$server\_port; > proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for; > proxy\_set\_header X-Forwarded-Proto $scheme; Are you sure Apache uses exactly the same headers when passing the request to the backend? Compare the frontend/backend traffic with apache and nginx, and adjust the nginx configuration accordingly. Nginx will do what you configure; but I guess the values above are not really inspected by your backend. > Guess it’s back to Apache since it handles it readily and has AJP support. Take a look at nginx\_ajp\_module: > **[GitHub - yaoweibin/nginx\_ajp\_module: support AJP protocol proxy with Nginx](https://github.com/yaoweibin/nginx_ajp_module#readme)** > > support AJP protocol proxy with Nginx Regards, Lukas ---
**Author:** ![solitaryr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@solitaryr](https://www.ruby-forum.com/u/solitaryr)\ **Post date:** [June 19, 2013, 3:29pm UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511/4 "2013-06-19T15:29:37Z")
On 19 June 2013 14:19, solitaryr [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Thanks, Lucas. We looked at the headers being passed back (that’s what the > jsp was for). Even with http completely disabled and https only available, > they were still passed as http:80 by nGinx…but Apache passed them through. I don’t understand what you mean by “passed as http:80”, but I think your problem will be fixable if you can provide more detailed information. Please post ascii dumps (tcpdump -nnn -A -s0 -i port 8080) of a request/response under nginx and then under apache, showing all HTTP headers in both directions. In that tcpdump example, I’m assuming your backend is listening for HTTP traffic on port 8080 - you may need to change that. Of course, redact anything you like, but please indicate where you’ve redacted something rather than just removing it. ## Jonathan Jonathan M. Oxford, London, UK > **[Jonathan Matthews :: Words Typed, Great Rates For Cash](https://www.jpluscplusm.com)** ---
**Author:** ![solitaryr](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/77aa72/32.png) [@solitaryr](https://www.ruby-forum.com/u/solitaryr)\ **Post date:** [June 19, 2013, 3:19pm UTC](https://www.ruby-forum.com/t/nginx-proxy-vs-apache-proxy/245511/5 "2013-06-19T15:19:41Z")
Thanks, Lucas. We looked at the headers being passed back (that’s what the jsp was for). Even with http completely disabled and https only available, they were still passed as http:80 by nGinx…but Apache passed them through. We tried this on two separate environments. I looked at the ajp module. Unfortunately, it’s not in any repository and custom builds are frowned upon for our systems. Posted at Nginx Forum: > **[Re: RE: nginx proxy vs apache proxy](https://forum.nginx.org/read.php?2,239872,240215#msg-240215)** > > I'm sure this is probably just a misconfiguration or a misunderstanding of nginx proxying. I'm looking to replace apache as my ssl/proxy server for a Jboss/tcServer backend. Unfortunately, I have a java web start app that builds the jnlp files...