Django not parsing query string if the question mark is escaped
Shouldn't Django be able to parse an escaped query string like so:
localhost:8000/sampleurl/myurl%3Fkey=value
like it was this:
localhost:8000/sampleurl/myrurl?key=value
Instead I'm getting a 404. This is the URL:
url(r'^sampleurl/(?P<slug>[-w]+)/$',
...
I was able to partially solve it by setting the url like so:
url(r'^sampleurl(?P<slug>[-w]+)(.*?)$',
...
But doesn't work 100% and it seems unnecessary.
django query-string django-urls
add a comment |
Shouldn't Django be able to parse an escaped query string like so:
localhost:8000/sampleurl/myurl%3Fkey=value
like it was this:
localhost:8000/sampleurl/myrurl?key=value
Instead I'm getting a 404. This is the URL:
url(r'^sampleurl/(?P<slug>[-w]+)/$',
...
I was able to partially solve it by setting the url like so:
url(r'^sampleurl(?P<slug>[-w]+)(.*?)$',
...
But doesn't work 100% and it seems unnecessary.
django query-string django-urls
2
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
1
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49
add a comment |
Shouldn't Django be able to parse an escaped query string like so:
localhost:8000/sampleurl/myurl%3Fkey=value
like it was this:
localhost:8000/sampleurl/myrurl?key=value
Instead I'm getting a 404. This is the URL:
url(r'^sampleurl/(?P<slug>[-w]+)/$',
...
I was able to partially solve it by setting the url like so:
url(r'^sampleurl(?P<slug>[-w]+)(.*?)$',
...
But doesn't work 100% and it seems unnecessary.
django query-string django-urls
Shouldn't Django be able to parse an escaped query string like so:
localhost:8000/sampleurl/myurl%3Fkey=value
like it was this:
localhost:8000/sampleurl/myrurl?key=value
Instead I'm getting a 404. This is the URL:
url(r'^sampleurl/(?P<slug>[-w]+)/$',
...
I was able to partially solve it by setting the url like so:
url(r'^sampleurl(?P<slug>[-w]+)(.*?)$',
...
But doesn't work 100% and it seems unnecessary.
django query-string django-urls
django query-string django-urls
asked Nov 14 '18 at 22:14
panoslpanosl
5841614
5841614
2
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
1
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49
add a comment |
2
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
1
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49
2
2
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
1
1
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309534%2fdjango-not-parsing-query-string-if-the-question-mark-is-escaped%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53309534%2fdjango-not-parsing-query-string-if-the-question-mark-is-escaped%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
no, the purpose of escaping a question mark is so that you don't use it as the query string delimiter.
– bryan60
Nov 14 '18 at 22:17
@bryan60 Some clients request it like that (ie, imagine an app requesting the url like the), is there a setting on Django (middleware) or apache, or will I need to solve that at a view level?
– panosl
Nov 14 '18 at 23:39
1
clients sending requests like that are breaking http. you could probably write a middlewear but you should just force your clients to follow http
– bryan60
Nov 15 '18 at 6:49