NGINX Webserver with Apache Reverse Proxy http2

Question

i have configued my Apache to act as a Reverse Proxy. Now i wanted to enabled http2 to speed it up.

Apache has the module enabled and Nginx also.

When i enter

Protocols h2 h2c http/1.1
ProtocolsHonorOrder Off

ProxyPass / h2://192.168.2.100/
ProxyPassReverse / https://192.168.2.100/

into the apache site configuration, Nginx throws a 400 Bad Request Error.

Using this code instead works:

Protocols h2 h2c http/1.1
ProtocolsHonorOrder Off
ProxyPass / https://192.168.2.100/
ProxyPassReverse / https://192.168.2.100/

Nginx Config:

listen 443 ssl http2;

How do i need to configure this section to work properly?#

JimP · Accepted Answer · 2021-10-04 16:42:16Z

3

I realize that this post is over a year old, but I ran into a similar issue after upgrading nginx to 1.20.1. Turns out that nginx was receiving multiple Host headers from Apache when HTTP2 was used. Adding RequestHeader unset Host resolved the issue.

answered Oct 4, 2021 at 16:42

JimP

312 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

adam-asdf · Accepted Answer · 2020-06-04 04:16:49Z

0

This is more a comment than an answer but it looks like you're new so maybe I can help (at the risk of being totally wrong).

I'm working on configuring Nginx as a reverse proxy for Apache to run a Django application (By the way, I have never heard of anyone using Apache as a reverse proxy for Nginx).

But there's some discussion in the Nginx documentation that makes me think it might not even be possible:

Reading through the Nginx docs on proxy_pass they mention how using websockets for proxying requires a special configuration

In that document it talks about how websockets requires HTTP1.1 (and an Upgrade and Connection HTTP header) so you can either basically fabricate them proxy_set_header between your server and proxy or you can pass them along if the client request includes them.

Presumably in this case, if the client didn't send the Upgrade header, you'd proxy_pass the connection to a server using TCP, rather than websockets.

Well, HTTP2 is (I assume) another Upgrade and one likely to have even less user agent support. So at the least, you'd risk compatibility problems.

Again, I have never configured Apache as a (reverse) proxy but my guess from your configuration is that Apache would handle the encryption to the client, then probably have to re-encrypt for the connection to Nginx.

That's a lot of overhead just on encryption, and probable browser compatibility issues...and probably not a great set up.

Again, I'm not sure if it's possible, I came here looking for a similar answer but you might want to reconsider.

answered Jun 4, 2020 at 4:16

adam-asdf

6567 silver badges16 bronze badges

2 Comments

Stef Over a year ago

Why shouldn't i use Apache as a Reverse Proxy? Nginx is not able to act as a reverse proxy and Nginx is running faster that Apache. Using Apache as Reverse Proxy and Nginx as a Webserver is a very good combination!

adam-asdf Over a year ago

I'd say this is a pretty good explanation of the differences and strengths of Nginx and Apache blog.martinfjordvald.com/nginx-primer-2-from-apache-to-nginx

Collectives™ on Stack Overflow

NGINX Webserver with Apache Reverse Proxy http2

2 Answers 2

Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related