Bug #2002
Search fails when it includes a slash
100%
Description
Try searching:
no/mou work:"new-testament"
Associated revisions
Adding test to make sure that the reverse proxy handles url encoding correctly
Reference #2002
Adding test to make sure that the reverse proxy handles url encoding correctly
Reference #2002
History
#1
Updated by Luke Murphey over 7 years ago
Updated by This is being encoded. I suspect that something is getting unescaped between Apache and the CherryPy server.
#2
Updated by Luke Murphey over 7 years ago
It looks like this: https://serverfault.com/questions/459369/disabling-url-decoding-in-nginx-proxy
Here is an Apache version: https://serverfault.com/questions/455060/cant-get-mod-proxy-to-correctly-forward-encoded-slash-characters-2f
#3
Updated by Luke Murphey over 7 years ago
Deploying nocanon and AllowEncodedSlashes to on prevents the 404 but the search still doesn't work.
#4
Updated by Luke Murphey over 7 years ago
The search query is coming through as no%2Fmou
#5
Updated by Luke Murphey over 7 years ago
Turns out nocanon wasn't necessary. This is working now.
#6
Updated by Luke Murphey over 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100