Re: Apache Http/Https reverse proxy based on content?

Hi Stefan,

The connection to the server (via a proxy) must be established before any of the content can be transferred.  Therefore, you can't use a different proxy based on the content.

Think of it this way:  If you wanted to call someone on the phone, it couldn't call a different phone number based on what language you're speaking.   You have to dial the phone number BEFORE you start talking -- it can't wait until after you're talking to figure out who to call.

Same with HTTP -- it has to connect BEFORE the content-type or the data can be transmitted.

-SK


On 1/12/23 8:44 AM, stefan@xxxxxxxxxx wrote:

Hi,


V7R4 soon to be V7R5.

A customer of mine has a bunch of Apache http-server instances running that are providing XML-data based on XML-requests from the outside world.

Now they want to serve json requests/responses as well from another set of Apache server instances.

Preferably they would like to use the existing external endpoints and route the incoming requests to different apache instances based on content type.


All incoming requests points at service.company.com

<me thinking out loud> If content ( payload ) is xml forward to xml.company.com

If content ( payload ) is json forward to json.company.com


I’ve been looking at ProxyPass and ProxyPassReverse but that seems to route based on endpoint hostname only.


Is anything like this possible?


All the best



Stefan Tageson