[MAGNOLIA-3976] disable x-magnolia-registration header in magnolia Created: 21/Feb/12 Updated: 23/Jul/15 Resolved: 03/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Thomas Sperger | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0.75d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 0.75d | ||
| 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)
|
| Date of First Response: |
| Description |
|
At every request the Magnolia CMS serves an additional X-Header is appended: One of our customer would like to disable this, but I didn't found any 1. Is this currently possible? How? Best Regards |
| Comments |
| Comment by Jan Haderka [ 21/Feb/12 ] |
|
This header is sent with every request on enterprise instance. |
| Comment by Edgar Vonk [ 22/Jul/15 ] |
|
Hi had, say that we would like to remove this header at some point: are there any side effects at all when we remove it? We are running Magnolia 5.x. |
| Comment by Jan Haderka [ 23/Jul/15 ] |
|
If you hide it w/ apache, there's no side effects. May I ask why you want to remove it? |
| Comment by Edgar Vonk [ 23/Jul/15 ] |
|
Thanks had! I don't want to remove it but sometimes some of our clients have very strict security requirements, one of which is that the websites we build should do everything possible to hide implementation details, including the CMS in which it was built. |