Ttdfjt

How do I remap "å" to type "å"?

Count the number of paths to n

Under what circumstances does intermodulation become an issue in a filter after LNA setup?

Why should a self-financing strategy be previsible?

Is it bad for SEO have the same site on a .gr and a .com with both English and Greek content?

Why can't you reverse the order of the input redirection operator for while loops?

Can an Arcane Focus be embedded in one's body?

How should i charge 3 lithium ion batteries?

Cost of oil sanctions to world's consumers

Talk interpreter

How many birds in the bush?

Was the Boeing 2707 design flawed?

Discussing work with supervisor in an invited dinner with his family

LINQ for generating all possible permutations

Hangman game in Python - need feedback on the quality of code

Expanding powers of expressions of the form ax+b

What are these white rings in the Undead parish?

Why is strlen so complex in C?

Breaker Mapping Questions

Do clerics commit a sin if they do not recite the liturgy of the hours?

Given current technology, could TV display screens double as video camera sensors?

Why did my folder names end up like this, and how can I fix this using a script?

How is linear momentum conserved in case of a freely falling body?

How do you capitalize agile costs with less mature teams?

Magento 1.9 Cookie is too large

Cookie Restriction Mode on EEErratic cookie-related login problemCustomer Login Doesn't Work in 1.9What's the correct cookie config for a Magento site split across multiple instances as subdomains?Inconsistent Cookies between www and non-www URLsUsers can' t login at https store because of double frontend cookieMagento In Subdirectory, Cookies being clearedUsers on IE and Edge have to log in twice on Magento 2 store

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

I am working on a fix to a website in the company that I work, and we got a report from one of the users that the site was taking too long to process things and was told that they got a message saying that cookies were too big.

I tried to buy several times on localhost, but everything sounds fine, I could not replicate or find a way to replicate this.

Anyone in here knows how to help me out with this?

Good help could be:

1. a tool that could help me to find this spot that is generating a huge cookie


2. any module that could prevent this big cookie issue


3. I suspect that the frontend cookie might be the issue if someone has any suggestions about this (but on localhost I can't see this growing, only on the live, so I might need to test solutions over there)


4. any tips for Nginx, I also think that might be Nginx configuration

magento-1.9 cookie

share|improve this question

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

add a comment | 

0

I am working on a fix to a website in the company that I work, and we got a report from one of the users that the site was taking too long to process things and was told that they got a message saying that cookies were too big.

I tried to buy several times on localhost, but everything sounds fine, I could not replicate or find a way to replicate this.

Anyone in here knows how to help me out with this?

Good help could be:

1. a tool that could help me to find this spot that is generating a huge cookie


2. any module that could prevent this big cookie issue


3. I suspect that the frontend cookie might be the issue if someone has any suggestions about this (but on localhost I can't see this growing, only on the live, so I might need to test solutions over there)


4. any tips for Nginx, I also think that might be Nginx configuration

magento-1.9 cookie

share|improve this question

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

add a comment | 

I am working on a fix to a website in the company that I work, and we got a report from one of the users that the site was taking too long to process things and was told that they got a message saying that cookies were too big.

I tried to buy several times on localhost, but everything sounds fine, I could not replicate or find a way to replicate this.

Anyone in here knows how to help me out with this?

Good help could be:

1. a tool that could help me to find this spot that is generating a huge cookie


2. any module that could prevent this big cookie issue


3. I suspect that the frontend cookie might be the issue if someone has any suggestions about this (but on localhost I can't see this growing, only on the live, so I might need to test solutions over there)


4. any tips for Nginx, I also think that might be Nginx configuration

magento-1.9 cookie

share|improve this question

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

share|improve this question

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

share|improve this question

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

asked Aug 14 at 11:41

Jose Rafael Mendes BarbosaJose Rafael Mendes Barbosa

111 bronze badge

1 Answer
1

active

oldest

votes

0

I imagine your user is getting 400 Bad Request, Cookie Too Large. It's a common error so there's quite a lot of leads I could find on Google.

My suggestion is to edit nginx configuration:

1. Find nginx virtualhost file in /etc/nginx/sites-available/ (For Linux)



2. 
   

   Add the config setting 'large_client_header_buffers' inside the server clause, like so:

   
   
   

   server
   # ...
   large_client_header_buffers 4 32k;
   # ...
   

   
   

Source: https://websiteforstudents.com/resolved-400-bad-request-request-header-or-cookie-too-large-via-nginx/

---

If the user keep complaining, you'll need to figure out how you can test this problem yourself. Perhaps nginx logs can provide more information when users are getting this error. Getting the referrer would be nice for you because then you know where the user is coming from when the error occurs.

share|improve this answer

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

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
);



);

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f285470%2fmagento-1-9-cookie-is-too-large%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

0

I imagine your user is getting 400 Bad Request, Cookie Too Large. It's a common error so there's quite a lot of leads I could find on Google.

My suggestion is to edit nginx configuration:

1. Find nginx virtualhost file in /etc/nginx/sites-available/ (For Linux)



2. 
   

   Add the config setting 'large_client_header_buffers' inside the server clause, like so:

   
   
   

   server
   # ...
   large_client_header_buffers 4 32k;
   # ...
   

   
   

Source: https://websiteforstudents.com/resolved-400-bad-request-request-header-or-cookie-too-large-via-nginx/

---

If the user keep complaining, you'll need to figure out how you can test this problem yourself. Perhaps nginx logs can provide more information when users are getting this error. Getting the referrer would be nice for you because then you know where the user is coming from when the error occurs.

share|improve this answer

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

add a comment | 

0

I imagine your user is getting 400 Bad Request, Cookie Too Large. It's a common error so there's quite a lot of leads I could find on Google.

My suggestion is to edit nginx configuration:

1. Find nginx virtualhost file in /etc/nginx/sites-available/ (For Linux)



2. 
   

   Add the config setting 'large_client_header_buffers' inside the server clause, like so:

   
   
   

   server
   # ...
   large_client_header_buffers 4 32k;
   # ...
   

   
   

Source: https://websiteforstudents.com/resolved-400-bad-request-request-header-or-cookie-too-large-via-nginx/

---

If the user keep complaining, you'll need to figure out how you can test this problem yourself. Perhaps nginx logs can provide more information when users are getting this error. Getting the referrer would be nice for you because then you know where the user is coming from when the error occurs.

share|improve this answer

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

add a comment | 

I imagine your user is getting 400 Bad Request, Cookie Too Large. It's a common error so there's quite a lot of leads I could find on Google.

My suggestion is to edit nginx configuration:

1. Find nginx virtualhost file in /etc/nginx/sites-available/ (For Linux)



2. 
   

   Add the config setting 'large_client_header_buffers' inside the server clause, like so:

   
   
   

   server
   # ...
   large_client_header_buffers 4 32k;
   # ...
   

   
   

Source: https://websiteforstudents.com/resolved-400-bad-request-request-header-or-cookie-too-large-via-nginx/

---

If the user keep complaining, you'll need to figure out how you can test this problem yourself. Perhaps nginx logs can provide more information when users are getting this error. Getting the referrer would be nice for you because then you know where the user is coming from when the error occurs.

share|improve this answer

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

share|improve this answer

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges

answered Aug 17 at 23:13

Anton OlssonAnton Olsson

322 bronze badges