@warren.strange wrote:
I am finding some weird behavior - which is puzzling me. It seems like warp does not properly handle 302 redirects (or maybe it is my app?)
The app has a landing page on /, and an admin page on /admin/
If you go directly to /admin/ (note trailing /) - it works as expected.The link on the landing page is to /admin (note - no trailing /) - which triggers the application to issue a 302 redirect to /admin/. It looks like the app sends the 302, but Cloudflare doesn’t send it back to the browser. The browser just throws up a CF error page complaining about a faulty dns name.
FWIW - The nginx ingress controller seems to handle this redirect just fine.
I also see this behaviour on another application. It sends a 302 - but the browser never sees it. But in this case, I can see CF request the 302 URL target - but the request never makes it back to the browser.
I tried fiddling with the ingress path (does it take wildcards? /* ) and the ingress.kubernetes.io/rewrite-target: / annotation. No substantial change.
Hints?