Re: Question on context().request().uri()
Re: Question on context().request().uri()
- Subject: Re: Question on context().request().uri()
- From: LD <email@hidden>
- Date: Fri, 2 Sep 2005 10:16:01 +1000
Hi Kieran,
On 02/09/2005, at 4:01 AM, Kieran Kelleher wrote:
Yes, that helps. I have found that when switching between HTTP and
HTTPS (my page subclass takes responsibility for this in
appendToResponse based on a page flag), I need to use
context.componentActionURL() (as per Marker's book) to build my
full redirect URL for a component action request and use
context.request().uri() (as per Chuck's book) to build my full
redirect URL for direct action requests.
Haven't seen these from WOContext's API?
- context().completeURLWithRequestHandlerKey(String key, String path,
String query, boolean isSecure, int port);
- context().urlWithRequestHandlerKey( String key, String path, String
query )
- context().directActionURLForActionNamed( String name, NSDictionary
query );
I found if I used context.request().uri() for HTTPS redirect URLs
for both type of requests, the component action request landed me
back on the same page. And I don't want to use componentActionURL
for direct action request redirects since that creates a session
So, I ended up using the request.requestHandlerKey() to determine
how to construct the redirect URL and it works fine, but I needed
to understand why.
See above.
with regards,
--
LD
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden