io.undertow.websockets.client.WebSocketClient contains an example of
how to use the CONNECT method, although we don't currently have any
way of then using the client over the created connection.
I think that ideally this would be implemented by enhancing the
existing client implementations, you should not really need a new
ClientProvider as the only real difference is in the connection
establishment.
Stuart
On Tue, Jul 18, 2017 at 1:23 AM, Kim Rasmussen <kr(a)asseco.dk> wrote:
Hi,
I have a usecase where I have a reverse proxy that uses a customized
ProxyHandler - for some hosts, I need to proxy the requests onwards via a
proxy server - e.g. a bluecoat proxy.
So something like this:
Browser --> Undertow reverse proxy --> Bluecoat Proxy --> Web server
So, I need to use the undertow client with a (non-reverse) proxy server.
I am guessing that with a ClientRequest, for non-ssl requests I should just
be able to change the path from /mypath to
http://my.server.name/mypath
before sending it to the proxy server instead of to the destination host
directly.
But what would be the ideal way of handling this when I need SSL so I need
to wrap the requests inside a "CONNECT my.server.name:443 HTTP/1.1" block
before starting the SSL negotiation ? Any pointers ?
Would creating a specific ClientProvider be a sensible way ?
--
Med venlig hilsen / Best regards
Kim Rasmussen
Partner, IT Architect
Asseco Denmark A/S
Kronprinsessegade 54
DK-1306 Copenhagen K
Mobile: +45 26 16 40 23
Ph.: +45 33 36 46 60
Fax: +45 33 36 46 61
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev