[
https://issues.apache.org/jira/browse/WW-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943058#comment-15943058
]
Stefaan Dutry commented on WW-4774:
-----------------------------------
[~lukaszlenart]
I had had a meeting with our system administrator at work to discuss this topic.
In case of a tomcat server the solution would have been to add a separate
connector (on a different port) and set the scheme to {{https}}. Then making
sure that this connector gets used when a request originating from https is
called.
This way if a call to getScheme() happens, it will result in https.
{code:xml|title=example from tomcat site}
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<Connector
protocol="org.apache.coyote.http11.Http11AprProtocol"
port="8443" maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
SSLCertificateFile="/usr/local/ssl/server.crt"
SSLCertificateKeyFile="/usr/local/ssl/server.pem"
SSLVerifyClient="optional" SSLProtocol="TLSv1+TLSv1.1+TLSv1.2"/>
{code}
Although this solution is possible when you are having full control over the
application server (and it's configuration) it's deployed on, i can imagine
plenty of cases where that's not the case.
Should i try to create 2 extra seperate resultTypes for people where the
previous is not an option?
for example:
* {{SSLAwareServletRedirectResult}}
* {{SSLAwareServletActionRedirectResult}}
> Upgrding Struts 2.3.1 to 2.5.10.1 - Redirect issues HTTPS to HTTP
> ------------------------------------------------------------------
>
> Key: WW-4774
> URL: https://issues.apache.org/jira/browse/WW-4774
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.5.10
> Reporter: upendar
> Priority: Critical
> Fix For: 2.5.next
>
>
> We are upgrading Struts2 from 2.3.1 to 2.5.10.1 ; redirect making https://
> to http:// . The following errors in chrome and IE are seen while redirecting
> from the popup to main window
> redirecting popup (create user) --- main window (viewdashboard) - the URL
> shows https:// to http://
> We are blocked completely due to this issue and need support ASAP. We also
> reviewed the apache server configurations and looks good. Please share the
> fix in detail.
> Error Issue in chrome :
> Mixed Content: The page at
> 'https://XXXXX/XX/XX/viewdashboard?clear&Id=1&uar=44' was loaded over HTTPS,
> but requested an insecure XMLHttpRequest endpoint
> 'http://XXX/XX/XX/viewdashboard?uar=44&Id=1'. This request has been blocked;
> the content must be served over HTTPS.
> Issue in IE
> SEC7127: Redirect was blocked for CORS request.
> File: account
> SCRIPT7002: XMLHttpRequest: Network Error 0x2ef1, Could not complete the
> operation due to error 00002ef1.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
