You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2001/05/12 23:00:51 UTC
Re: cvs commit: jakarta-struts/src/share/org/apache/struts/util
RequestUtils.java
Craig,
Speaking of schemes, any advice on the easiest way to flip between http:
and https: -- the context being able to offer the option of logging in
securely under https:, and then returning to http: afterwards.
Yahoo! Auctions does this, and I'm trying to do that same at
< http://data.wxxi.org/wxxi-gavel/ >
See also
<
http://www.mail-archive.com/struts-user%40jakarta.apache.org/msg07841.html
>
-Ted.
To SSL and back again
Posted by Ted Husted <hu...@apache.org>.
"Craig R. McClanahan" wrote:
> You can calculate an absolute URL for this web app, based on things like
> request.getServerName(), request.getContextPath(), and so on. So, one way
> to do this would be to have an action that calculated the new absolute
> URL, wrapped it in a new ActionForward with the "redirect" property set,
> and return that to the controller servlet. It looks pretty much like what
> you quoted in the mail message.
I embedded the absolute URL in the config to get started.
If seems like the best overall approach right now, I'll work out
calculating it at runtime, and smoothing out the procedure, and update
the SSL FAQ.
> NOTE: Because the controller servlet calls encodeRedirectURL() for you on
> redirections, sessions should survive across this transfer whether or not
> you are using cookies.
Yes, they do, which is very cool.
See also
http://www.mail-archive.com/struts-user%40jakarta.apache.org/msg07841.html
To SSL and back again
Posted by Ted Husted <hu...@apache.org>.
"Craig R. McClanahan" wrote:
> You can calculate an absolute URL for this web app, based on things like
> request.getServerName(), request.getContextPath(), and so on. So, one way
> to do this would be to have an action that calculated the new absolute
> URL, wrapped it in a new ActionForward with the "redirect" property set,
> and return that to the controller servlet. It looks pretty much like what
> you quoted in the mail message.
I embedded the absolute URL in the config to get started.
If seems like the best overall approach right now, I'll work out
calculating it at runtime, and smoothing out the procedure, and update
the SSL FAQ.
> NOTE: Because the controller servlet calls encodeRedirectURL() for you on
> redirections, sessions should survive across this transfer whether or not
> you are using cookies.
Yes, they do, which is very cool.
See also
http://www.mail-archive.com/struts-user%40jakarta.apache.org/msg07841.html
Re: cvs commit: jakarta-struts/src/share/org/apache/struts/util
RequestUtils.java
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Sat, 12 May 2001, Ted Husted wrote:
> Craig,
>
> Speaking of schemes, any advice on the easiest way to flip between http:
> and https: -- the context being able to offer the option of logging in
> securely under https:, and then returning to http: afterwards.
>
You can calculate an absolute URL for this web app, based on things like
request.getServerName(), request.getContextPath(), and so on. So, one way
to do this would be to have an action that calculated the new absolute
URL, wrapped it in a new ActionForward with the "redirect" property set,
and return that to the controller servlet. It looks pretty much like what
you quoted in the mail message.
NOTE: Because the controller servlet calls encodeRedirectURL() for you on
redirections, sessions should survive across this transfer whether or not
you are using cookies.
If you're running on ports other than the default (80 and 443), you will
probably also want a configuration parameter to define what the
corresponding SSL and non-SSL ports are.
> Yahoo! Auctions does this, and I'm trying to do that same at
>
> < http://data.wxxi.org/wxxi-gavel/ >
>
> See also
>
> <
> http://www.mail-archive.com/struts-user%40jakarta.apache.org/msg07841.html
> >
>
> -Ted.
>
Craig