[MAGNOLIA-3329] Redirecting to https with Blossom Created: 20/Oct/10 Updated: 17/Dec/10 Resolved: 17/Dec/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.3.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Christian Haddorp | Assignee: | Boris Kraft |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I'm not sure if it's an error - it's more a support question Beside the Admin Central our application does redirects. We us Blossom... So, a redirect looks like the following. The site is completely HTTPS. However the redirect is built as HTTP. The SSL cert is installed on the Webserver; not on the Tomcat - that is used as application server. I've attached the Tomcat server.xml. Do you see any misconfiguration that might cause this issue? It there anything we can configure within Magnolia? |
| Comments |
| Comment by Tobias Mattsson [ 20/Oct/10 ] |
|
I'm not an expert on apache configurations but i believe that you can configure rewriting of redirects using mod_proxy and setting ProxyPassReverse. Though this assumes that you're using apache. Btw, you don't have to add the context path yourself, use |
| Comment by Magnolia International [ 17/Dec/10 ] |
|
Please reopen and move this issue to the SUPPORT project. Unless it's an actual issue with BLOSSOM, in which case the issue will be copied/moved there. |