How to remove cookie data from static content request?
I have created a separate domain to serve static content. Also modified URL values in System->Configuration->General->Web.
When I inspect any static content request with firebug in firefox browser, I can see frontend and adminhtml cookies data are also attached to that request.
I want to remove that cookie data from request. How can I achieve this?
magento-1.9 url cookie
add a comment |
I have created a separate domain to serve static content. Also modified URL values in System->Configuration->General->Web.
When I inspect any static content request with firebug in firefox browser, I can see frontend and adminhtml cookies data are also attached to that request.
I want to remove that cookie data from request. How can I achieve this?
magento-1.9 url cookie
1
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25
add a comment |
I have created a separate domain to serve static content. Also modified URL values in System->Configuration->General->Web.
When I inspect any static content request with firebug in firefox browser, I can see frontend and adminhtml cookies data are also attached to that request.
I want to remove that cookie data from request. How can I achieve this?
magento-1.9 url cookie
I have created a separate domain to serve static content. Also modified URL values in System->Configuration->General->Web.
When I inspect any static content request with firebug in firefox browser, I can see frontend and adminhtml cookies data are also attached to that request.
I want to remove that cookie data from request. How can I achieve this?
magento-1.9 url cookie
magento-1.9 url cookie
edited Sep 11 '15 at 8:22
Fabian Schmengler
54.2k20129340
54.2k20129340
asked Aug 27 '15 at 12:03
piyush_systematixpiyush_systematix
92921730
92921730
1
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25
add a comment |
1
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25
1
1
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25
add a comment |
1 Answer
1
active
oldest
votes
You also have to set the cookie domain explicitly in System > COnfiguration > General > Web > Session Cookie Management:
If you leave it empty, Magento uses .example.com
with a leading dot, which also matches all subdomains.
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot onform_key
andPHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler
– Keyur Shah
Jul 31 '18 at 12:26
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fmagento.stackexchange.com%2fquestions%2f80084%2fhow-to-remove-cookie-data-from-static-content-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You also have to set the cookie domain explicitly in System > COnfiguration > General > Web > Session Cookie Management:
If you leave it empty, Magento uses .example.com
with a leading dot, which also matches all subdomains.
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot onform_key
andPHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler
– Keyur Shah
Jul 31 '18 at 12:26
add a comment |
You also have to set the cookie domain explicitly in System > COnfiguration > General > Web > Session Cookie Management:
If you leave it empty, Magento uses .example.com
with a leading dot, which also matches all subdomains.
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot onform_key
andPHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler
– Keyur Shah
Jul 31 '18 at 12:26
add a comment |
You also have to set the cookie domain explicitly in System > COnfiguration > General > Web > Session Cookie Management:
If you leave it empty, Magento uses .example.com
with a leading dot, which also matches all subdomains.
You also have to set the cookie domain explicitly in System > COnfiguration > General > Web > Session Cookie Management:
If you leave it empty, Magento uses .example.com
with a leading dot, which also matches all subdomains.
answered Sep 11 '15 at 8:24
Fabian SchmenglerFabian Schmengler
54.2k20129340
54.2k20129340
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot onform_key
andPHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler
– Keyur Shah
Jul 31 '18 at 12:26
add a comment |
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot onform_key
andPHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler
– Keyur Shah
Jul 31 '18 at 12:26
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
I've noticed on cookie path change, the affect is not reflecting on storefront unless the cookies are removed. And to ask store customers to delete their cookies is not a practical solution. Is there a way to make the changes (related to cookie) reflect instantly for customers?
– R T
May 10 '18 at 12:03
1
1
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
You could do it with a temporary Javascript that deletes the cookie with the old values
– Fabian Schmengler
May 11 '18 at 7:09
I tried the same thing but still, it adds a leading dot on
form_key
and PHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler– Keyur Shah
Jul 31 '18 at 12:26
I tried the same thing but still, it adds a leading dot on
form_key
and PHPSESSID
cookie, do you have any idea for this? or is this correct behavior? as we have multiple stores and we don't want to share cookie across domains @FabianSchmengler– Keyur Shah
Jul 31 '18 at 12:26
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- 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%2fmagento.stackexchange.com%2fquestions%2f80084%2fhow-to-remove-cookie-data-from-static-content-request%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
1
Please take your time to accept an answer if it helped you. magento.stackexchange.com/help/someone-answers
– Fabian Schmengler
Dec 18 '15 at 15:25