WebPositive ignores Proxy settings

[egrath]

WebPositive ignores the Proxy settings completly.

Steps to reproduce:

1. Set up a proxy server somewhere
2. Configure W+ to use this proxy

If you use tcpdump to monitor the outgoing packets there's no indication that W+ is using the proxy, instead direct connections to the host given by the URL are made. It even doesn't matter if you set the environment variables http_proxy and https_proxy and start W+ within this context.

I'm using hrev47380.

[pulkomandy]

The next version of WebKit will support proxies again. I went with the most basic HTTP or HTTPS solution, no SOCKS for now. Also the proxy authentication (username and password) aren't supported. Does anyone need these?

[waddlesplash]

No response, and the "next version" of WebKit was deployed in hrev47920. Closing as fixed.

[pulkomandy]

Wait, what? Half the feature is still missing. You can't proxy to HTTPS right now (this needs either a "bypass proxy" mode or SOCKS support).

I can close my tickets myself when I'm done, thanks.

[Giova84]

As described in #11413 (sorry for the dup), I'm currently using an HTTP proxy in WebPositive (on hrev48215), but differently from this ticket, at least for me, WebPositive doesn't ignore the proxy every time: sometimes WebPositive is able to accept the proxy's directives, and the most of the time acts like if no proxy were used.

[dac324]

May sound like a stupid question: How can I watch this ticket?

[pulkomandy]

You just subscribed by commenting on it, you should get mail notifications now.

[pulkomandy]

HTTPS proxy support (through CONNECT) implemented in hrev49808 but untested. Please test and report.

[Anarchos]

​http://xref.plausible.coop/source/xref/haiku/src/apps/webpositive/SettingsWindow.cpp#455 I think it should be kSettingsKeyProxyPort.

[simonsouth]

This appears to still be an issue in Haiku hrev49940 (x86_gcc2): WebPositive seems to be ignoring the proxy settings completely.

[diver]

(In #13392) Dupe of #10973

[waddlesplash]

HTTP proxy support works as of hrev52050. HTTPS proxying does not work, and usually results in a "Bad data" error message. Here's an example error message from the proxy server I was testing with:

2018/07/01 22:23:41 proxy-http failed to dial: dial tcp 10.0.2.2:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

PulkoMandy, if you have to investigate, the proxy I was testing with was ​https://github.com/nadoo/glider which is very simple to use. It does indeed support CONNECT: ​https://github.com/nadoo/glider/blob/master/proxy/http/http.go#L109