I have a front end API which I want to use to proxy/redirect requests to a
backend service. Up until now, I've been binding the APIs using the {rr}
technique described in the documentation, but the main issue I have is that I
am binding to the backend service's host/port at startup (in
Hello,
I have a Restlet application that needs to connect through a proxy (Tinyproxy,
https://banu.com/tinyproxy/) for outgoing HTTP(S) connections. I'm using the
Apache HttpClient connector and it works just fine for direct HTTP, direct
HTTPS and proxied HTTP connections.
But proxied HTTPS
Subclass Redirector, overriding getTargetRef(Request, Response) to return a
Reference that you determine dynamically from the request and response
parameters.
--tim
On Mon, Apr 15, 2013 at 10:06 PM, Grant gsing...@apache.org wrote:
I have a front end API which I want to use to proxy/redirect
Hi all,
Here is an update following the server failure we had back in January:
- The Maven repository http://maven.restlet.org/ has been fully
restored
- we will work next of synchronizing it with the central repository
- thanks to Tamas Caservenak from Sonatype for his recent
That works beautifully, thank you!
For the record, I used what was in getTargetRef almost as is, except I replaced
the baseRef with a dynamically discovered one (that I get from Zookeeper).
Thanks,
Grant
--
Jerome,
thanks for your reply. Yes, I was not aware of the html redirect, as I have
always used server side. I suppose that would work, but it does seem that
serverside is a more recommended method.
My pattern is that an HTML FORM submits a POST, and depending on the
circumstance, issues a
6 matches
Mail list logo