Bypassing proxy servers

Proxys are a pretty annoying configuration headache for us when we have to debug connection issues with customers. Is the an existing feature of SS that will bypass proxy servers (I assume not using http is sufficient)?

Proxies can be annoying and unfortunately dealing with them can vary largely depending on how they are setup and what they are designed to do.

Bypassing a proxy will be up to how traffic gets to/from the SS server (network architecture) and not the server itself. If you are using the JsonServiceClient you can tell it to use your specific proxy settings, but I don’t think this is what you are trying to do.

Right, normally proxies are opt-in where you can specify a proxy for the Service Client’s by setting JsonServiceClient.Proxy property or configuring it in your .NET App by specifying it in the web.config, see: https://msdn.microsoft.com/en-us/library/kd3cf2ex(v=vs.110).aspx

Other than that you can make ServiceStack act like a proxy itself, see: https://github.com/ServiceStack/ServiceStack/blob/master/docs/2015/release-notes.md#using-servicestack-as-a-proxy

But not sure if that’s what you want.

If I opt out of using the proxy, SS will be blocked because all http has to go through the proxy or it gets blocked - that’s the normal configuration I’ve had experience with.

We use auto configuration of the proxy, but it’s not always reliable, I have a windows service that is installed as Local System, which usually has some forgotten proxy settings defined or none at all, which involves getting IT to run IE as Local System to access and configure proxy settings.

Other times, clients just have to whitelist the url’s/ ip’s we are accessing, not good for long term stability or short term productivity.

Other times, we ask IT to check the proxy settings and it takes a few rounds of convincing them the proxy/ firewall/ endpoint protection is the problem before they find the correct settings to let traffic through.

I have noticed that using a SSH tunnel or other non http protocols over port 80 will get past the proxy and firewall, presumably because the proxy doesn’t understand the protocol, it just lets non http traffic bypass it, and the firewall just lets port 80/ 443 through.

To summarise, I think that if SS provided a non standard ssl/http protocol, it would get past proxy servers and firewalls much easier.

This sounded like it may achieve the end result I’m looking for: