Monday, December 31, 2001 03:51 AM
Deft handling of HTTPS is a blind spot in the framework.
I do think we need a better all-around solution for this.
For now, you could set up alternate struts-config's for each
host, and then edit the web.xml when its deployed. But
that's really messy. The entity in the DTD is a clever idea
but that also requires editing the configuration after it is
Another alternative would be to use a utility method
in the Action which turned the context relative path
into an absolute path using a specified scheme and port.
Something that looked like this:
HttpServletRequest request, ActionForward forward,
String scheme, String port)
So this would return a new ActionForward based on the first,
but with an adjusted path.
In the Action, you could call it like this:
return newForwardAbsolute(request, mapping.findForward("continue"), "HTTPS", "");
If you do anything like this, please consider contributing it
back to the community as an
enhancement request to
HTH - Ted