You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that I cannot access the administration interface from _utils. Attempting to navigate to, for instance, example.com/e=_/_utils, would result in the URI being stripped to just example.com/_utils, and being given an "Access denied", meaning it was being caught by the Caddy path handler for all non e=_ access.
I was eventually able to figure out that simply adding an additional / to the URI, such as example.com/e=_/_utils/, would give me access, but I'd be interested to know if this is replicable, and if so, perhaps the documentation should be updated to mention it.
Of note, I am using a native Caddy server, with the headers from the example docker-compose translated into a Caddyfile configuration, as mentioned in #8.
The text was updated successfully, but these errors were encountered:
I found that I cannot access the administration interface from _utils. Attempting to navigate to, for instance, example.com/e=_/_utils, would result in the URI being stripped to just example.com/_utils, and being given an "Access denied", meaning it was being caught by the Caddy path handler for all non e=_ access.
I was eventually able to figure out that simply adding an additional / to the URI, such as example.com/e=_/_utils/, would give me access, but I'd be interested to know if this is replicable, and if so, perhaps the documentation should be updated to mention it.
Of note, I am using a native Caddy server, with the headers from the example docker-compose translated into a Caddyfile configuration, as mentioned in #8.
The text was updated successfully, but these errors were encountered: