Topic: Configure Apache HTTP Server to support non-SSL technologies

[ShaoChan]

Hi there,

I have a legacy technology that needs to talk to a HTTPS endpoint (https://api.somesite.com).

It can reach out to a HTTP endpoint (http://api.somesite.com), but not HTTPS.

Essentially the legacy app does not understand SSL certificates and does not support cipher suites and thus can only communicate on HTTP.

Ideally, I'd like to configure Apache HTTP Server so that:
Legacy App --> Apache as a proxy server --> Actual Destination.

This requires Apache to initiate the SSL connection when a HTTP request comes in from the legacy client.

Is this possible? The solution does not need to be generic (i.e. does not require that all http requests are forwarded to its equivalent https address) - it can simply a single hard-coded configuration so that the legacy client calls Apache on port 80 and it is hard-coded to reach https://api.somesite.com on port 443.

If so, could someone highlight the httpd.conf changes needed (based on the latest v2.4 server) please.

Thanks,

Shao

[James Blond]

A simple reverse vhost would do the job.

[ShaoChan]

Thanks James. Does the SSLEngine config need to be made? Have you configured this before and got HTTP to HTTPS traffic working? Thanks.

[James Blond]

[ShaoChan]

Thanks James!