Here's an obscure corner case. Is it possible to use Synapse in the role of an HTTP proxy, or at least have it look like one to clients? What I'm going for is to have Synapse get requests for fully qualified urls (ie, 'GET http://www.example.com/stuff HTTP/1.1') and do it's normal mediation shtick on them.
It seems like this is doable with SOAP/POX requests, as Synapse seems to expect HTTP proxy-style POST-with-fully-qualified-url requests when not serving a Synapse <proxy> service. However, when doing the same with a GET request, it of course responds with a Moved Permanently redirect to the services index page because it thinks some poor misdirected user is aiming a web browser at the wrong place. I've looked at the ServerWorker class that handles this, and while hacking out the redirect sending code seems pretty straightforward, the result is then that GET requests of this type just hang (GETting something served by a <proxy> service still works). Is it possible to make Synapse work in this way, or is this just excessively an abuse of what synapse is supposed to do? Thanks, -Leander
