Routing fails on Apache Webserver
Posted: 29 Aug 2019, 08:24
I integrated the Aimeos Shop in my NEOS site and finally wanted to deploy it to the live server. The admin interface is secured by Policy.yaml as described here: https://github.com/aimeos/aimeos-flow/issues/16
On the final system, I recognized routing issues in the admin interface, where encoded slashes are part of the url, e.g. (%2f):
https://abc.de/anypath/locale%2fcurrency?lang=en
-> leads to a "Not found" page
After some research, I found out that Apache does not allow this by default, but needs the setting "AllowEncodedSlashes" set to "On". As my hoster doesn't allow this and this can't be set in the .htaccess file, my question if there is any workaround?
--
Also queries to the jsonadm end in a 403 (Forbidden), but I guess this is something different related to a CORS problem not handled by the Flow Wrapper,
On the final system, I recognized routing issues in the admin interface, where encoded slashes are part of the url, e.g. (%2f):
https://abc.de/anypath/locale%2fcurrency?lang=en
-> leads to a "Not found" page
After some research, I found out that Apache does not allow this by default, but needs the setting "AllowEncodedSlashes" set to "On". As my hoster doesn't allow this and this can't be set in the .htaccess file, my question if there is any workaround?
--
Also queries to the jsonadm end in a 403 (Forbidden), but I guess this is something different related to a CORS problem not handled by the Flow Wrapper,