-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
custom_base_url vs assets base-url and page lookup #3511
Comments
Same here. In final case i would like if possible to rewrite-target on my proxy (so i'm suppose to set empty Here is my config for final case :
This is what i expect: <link href="user/plugins/markdown-notices/assets/notices.css" type="text/css" rel="stylesheet"> This is what i have: <link href="/user/plugins/markdown-notices/assets/notices.css" type="text/css" rel="stylesheet"> It seams like if |
grav/system/src/Grav/Common/Uri.php Line 245 in 720a965
I'm not a PHP expert but i don't think we should add rootURL on relative URI here ... |
Whenever I setup a custom base url I can't get Grav to work (starting with 1.7)
I'm getting the opposite behavior described in #3238
Setup:
https://mydomain.com/foo/ -> [reverse proxy to http://127.0.0.4:8000/] -> Grav
custom_base_url: /foo
was fine.custom_base_url
: Assets are missing (looked for athttps://mydomain.com/
withoutfoo/
)custom_base_url: /foo
: Pages are not found (even /foo/admin is not found)custom_base_url
clearly affects pages retrieval (and more generally, the whole routing process), but I can't find how to make it work.Help very welcomed!
The text was updated successfully, but these errors were encountered: