Location
returned by redirect_slashes
should be relative instead of absolute
#2651
Unanswered
rijenkii
asked this question in
Potential Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a following setup:
When a browser accidentally calls an endpoint without an ending slash, Starlette responds with a 307 with
Location: http://example.org/api/endpoint/
, which browser rightfully rejects because of mixed content blocking.If Starlette responded with
Location: /api/endpoint/
instead, browser would then just slap that relative location to the current host.Django does it like that, but they respond with 301s:
Beta Was this translation helpful? Give feedback.
All reactions