Bug 64995 - proxypass to ssl target through proxyremote not set correcly the sni_hostname....
Summary: proxypass to ssl target through proxyremote not set correcly the sni_hostname...
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.4.23
Hardware: PC Linux
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-16 19:35 UTC by Mathieu CARBONNEAUX
Modified: 2020-12-16 20:17 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu CARBONNEAUX 2020-12-16 19:35:45 UTC
When i use proxy to https target with ProxyRemote (with ProxyPreservehost off) apache set in ssl servername the proxy name in place of the ProxyPass hostname. 

https://httpd.apache.org/docs/2.4/fr/mod/mod_proxy.html#proxypass
https://httpd.apache.org/docs/2.4/fr/mod/mod_proxy.html#proxyremote
https://httpd.apache.org/docs/2.4/fr/mod/mod_proxy.html#proxypreservehost
https://httpd.apache.org/docs/2.4/fr/mod/mod_ssl.html#sslproxyengine

Exemple:

SSLProxyEngine on

ProxyRemote "*" "http://cleverproxy.localdomain:8080"
ProxyPass / https://mytarget/


This set cleverproxy.localdomain:8080 in ssl servername.
Comment 1 Ruediger Pluem 2020-12-16 20:17:19 UTC
This looks like a duplicate of PR57139 and should be fixed in your version. Are you really sure that you use 2.4.23 and not something below 2.4.12?
Anyway can you please retest with the latest version 2.4.46?