Bug #21278
closed
Redirect loop when refreshing search results
Description
Steps to reproduce:
- Search for something in Workbench
- Once you're on the results page, refresh the page in your browser
Expected result: The page refreshes and shows your results again
Actual result: The browser shows a built-in error page to report "This page isn't redirecting properly"
Updated by Peter Amstutz 5 months ago
- Target version changed from Future to Development 2024-01-17 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
Updated by Peter Amstutz 5 months ago
- Target version changed from Development 2024-01-31 sprint to Development 2024-01-17 sprint
Updated by Stephen Smith 4 months ago
I noticed this doesn't happen locally, using curl -v it looks like the immediate response to any /search-results path gives a 302 redirect to the same url without sending any workbench code. This might be an nginx configuration issue
Updated by Peter Amstutz 4 months ago
- Assigned To set to Peter Amstutz
Check if this is actually a bug in the nginx redirects for wb1 to wb2 paths.
Updated by Tom Clegg 4 months ago
Indeed, one of our redirect rules in source:sdk/python/tests/nginx.conf copied from source:tools/salt-install/config_examples/multi_host/aws/pillars/nginx_workbench_configuration.sls is
^/search.* /search-results;
...which is a redirect loop.
Updated by Peter Amstutz 4 months ago
21278-search-redirect @ a22d01b7133be84a38914ab98a19d4e5aba07d50
Just removes the redirect, it doesn't add enough value to try and make it work.
Updated by Peter Amstutz 4 months ago
- Status changed from In Progress to Resolved