When HTTPS connection has sent secure XSRF cookie, HTTP connection cannot overwrite it (Chrome and Firefox)
I'm using Angular's $httpProvider and taking advantage of the cross-site request forgery protection it provides. As the documentation explains:
[Your] server needs to set a token in a JavaScript readable session cookie called XSRF-TOKEN on the first HTTP GET request. On subsequent XHR requests the server can verify that the cookie matches the X-XSRF-TOKEN HTTP header [that the $httpProvider has set based on the cookie], and therefore be sure that only JavaScript running on your domain could have sent the request.
This works beautifully if a user is only connecting to our application via HTTPS or only connecting via HTTP. But if a user connects via HTTPS and their browser has the secure XSRF-TOKEN cookie, when they try to connect via HTTP later, Chrome and Firefox will ignore the new cookie because these browsers refuse to replace a secure cookie with an insecure one with the same name and domain (I can't find documentation on this for either browser anywhere but it's totally happening).
Of course ideally we would expire the XSRF-TOKEN cookie when the user's session ends, but that proves pretty difficult when there are many threads for various Web service calls returning at different times, not necessarily with the newest cookie information.
I've worked around the problem by naming the cookie differently between HTTPS and HTTP, but is there a neater way to do this?
google-chrome firefox cookies https csrf asked Nov 13 '18 at 1:32
melanie johnson
337213
add a comment |
I'm using Angular's $httpProvider and taking advantage of the cross-site request forgery protection it provides. As the documentation explains:
[Your] server needs to set a token in a JavaScript readable session cookie called XSRF-TOKEN on the first HTTP GET request. On subsequent XHR requests the server can verify that the cookie matches the X-XSRF-TOKEN HTTP header [that the $httpProvider has set based on the cookie], and therefore be sure that only JavaScript running on your domain could have sent the request.
This works beautifully if a user is only connecting to our application via HTTPS or only connecting via HTTP. But if a user connects via HTTPS and their browser has the secure XSRF-TOKEN cookie, when they try to connect via HTTP later, Chrome and Firefox will ignore the new cookie because these browsers refuse to replace a secure cookie with an insecure one with the same name and domain (I can't find documentation on this for either browser anywhere but it's totally happening).
Of course ideally we would expire the XSRF-TOKEN cookie when the user's session ends, but that proves pretty difficult when there are many threads for various Web service calls returning at different times, not necessarily with the newest cookie information.
I've worked around the problem by naming the cookie differently between HTTPS and HTTP, but is there a neater way to do this?
google-chrome firefox cookies https csrf asked Nov 13 '18 at 1:32
melanie johnson
337213
add a comment |
I'm using Angular's $httpProvider and taking advantage of the cross-site request forgery protection it provides. As the documentation explains:
[Your] server needs to set a token in a JavaScript readable session cookie called XSRF-TOKEN on the first HTTP GET request. On subsequent XHR requests the server can verify that the cookie matches the X-XSRF-TOKEN HTTP header [that the $httpProvider has set based on the cookie], and therefore be sure that only JavaScript running on your domain could have sent the request.
This works beautifully if a user is only connecting to our application via HTTPS or only connecting via HTTP. But if a user connects via HTTPS and their browser has the secure XSRF-TOKEN cookie, when they try to connect via HTTP later, Chrome and Firefox will ignore the new cookie because these browsers refuse to replace a secure cookie with an insecure one with the same name and domain (I can't find documentation on this for either browser anywhere but it's totally happening).
Of course ideally we would expire the XSRF-TOKEN cookie when the user's session ends, but that proves pretty difficult when there are many threads for various Web service calls returning at different times, not necessarily with the newest cookie information.
I've worked around the problem by naming the cookie differently between HTTPS and HTTP, but is there a neater way to do this?
google-chrome firefox cookies https csrf asked Nov 13 '18 at 1:32
melanie johnson
337213
I'm using Angular's $httpProvider and taking advantage of the cross-site request forgery protection it provides. As the documentation explains:
[Your] server needs to set a token in a JavaScript readable session cookie called XSRF-TOKEN on the first HTTP GET request. On subsequent XHR requests the server can verify that the cookie matches the X-XSRF-TOKEN HTTP header [that the $httpProvider has set based on the cookie], and therefore be sure that only JavaScript running on your domain could have sent the request.
This works beautifully if a user is only connecting to our application via HTTPS or only connecting via HTTP. But if a user connects via HTTPS and their browser has the secure XSRF-TOKEN cookie, when they try to connect via HTTP later, Chrome and Firefox will ignore the new cookie because these browsers refuse to replace a secure cookie with an insecure one with the same name and domain (I can't find documentation on this for either browser anywhere but it's totally happening).
Of course ideally we would expire the XSRF-TOKEN cookie when the user's session ends, but that proves pretty difficult when there are many threads for various Web service calls returning at different times, not necessarily with the newest cookie information.
I've worked around the problem by naming the cookie differently between HTTPS and HTTP, but is there a neater way to do this?
google-chrome firefox cookies https csrf google-chrome firefox cookies https csrf asked Nov 13 '18 at 1:32
melanie johnson
337213
asked Nov 13 '18 at 1:32
melanie johnson
337213
asked Nov 13 '18 at 1:32
melanie johnson
337213
asked Nov 13 '18 at 1:32
melanie johnson
337213
asked Nov 13 '18 at 1:32
melanie johnson
337213
337213
add a comment |
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%2f53272485%2fwhen-https-connection-has-sent-secure-xsrf-cookie-http-connection-cannot-overwr%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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53272485%2fwhen-https-connection-has-sent-secure-xsrf-cookie-http-connection-cannot-overwr%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
