[MAGNOLIA-5903] 401 Status code for .magnolia makes usage of custom errordocuments in Apache impossible Created: 03/Sep/14  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 5.2.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Martin Mörner Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 14.04 with Apache 2.4.7


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   

Usage of Apache as proxy server with the follwoing configuration:

Alias                   /404    /var/www/404
ErrorDocument           404     /404/server-error.html

ProxyErrorOverride      on
ProxyRequests           off
ProxyPass               /404            !
ProxyPass               /       ajp://localhost:8009/   max=200 retry=7

makes it impossible to access the admin interface for login due to the send 401 status code. As the ProxyErrorOverride applies to all error pages (400-500) and uses the standard Apache ErrorDocument for the given 401.

As far as I understand the RFC2616 the 401 code should only be used for basic authorization or digests. For a normal web page login a 200 OK would be more suitable and makes it possible to use Magnolia inside Apache Tomcat to be proxied over AJP.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:09:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.