Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

413 Request Entity Too Large (history)

  • 7 amsoshi
  • 7 sa na da wannan matsala
  • 1 view
  • Amsa ta ƙarshe daga JEmlay

JEmlay
JEmlay
more options

I started getting a sync error that wouldn't go away. When I looked at the log I saw a bunch of post errors. So the first thing I tried was to blow everything out since I was using the old sync. I then setup the new sync but I still had an error. Only this time it was only one post failure and History was specifically the problem:

1412870549016 Sync.Collection DEBUG POST Length: 2152216 1412870551015 Sync.Collection DEBUG mesg: POST fail 413 https://sync-141-us-west-2.sync.services.mozilla.com/1.5/10221627/storage/history 1412870551015 Sync.Collection DEBUG POST fail 413 https://sync-141-us-west-2.sync.services.mozilla.com/1.5/10221627/storage/history 1412870551015 Sync.Engine.History DEBUG Uploading records failed: 413 Request Entity Too Large

If I turn off history then all is well and it syncs fine. But of course now I can't sync my history. Any ideas on how to fix this? Am I stuck having to blow out my history?

I started getting a sync error that wouldn't go away. When I looked at the log I saw a bunch of post errors. So the first thing I tried was to blow everything out since I was using the old sync. I then setup the new sync but I still had an error. Only this time it was only one post failure and History was specifically the problem: 1412870549016 Sync.Collection DEBUG POST Length: 2152216 1412870551015 Sync.Collection DEBUG mesg: POST fail 413 https://sync-141-us-west-2.sync.services.mozilla.com/1.5/10221627/storage/history 1412870551015 Sync.Collection DEBUG POST fail 413 https://sync-141-us-west-2.sync.services.mozilla.com/1.5/10221627/storage/history 1412870551015 Sync.Engine.History DEBUG Uploading records failed: 413 Request Entity Too Large If I turn off history then all is well and it syncs fine. But of course now I can't sync my history. Any ideas on how to fix this? Am I stuck having to blow out my history?

Mafitar da aka zaɓa

So anyway....went ahead and blew out the history cache. I guess it'll just keep on happening as the history gets too large and there's no real fix for this.

Karanta wannan amsa a matsayinta 👍 1

All Replies (7)

guigs
guigs
more options

Hi JEmlay, How big is your places.sqlite file in your profile folder? Profiles - Where Firefox stores your bookmarks, passwords and other user data

JEmlay
JEmlay Mai mallakar tambaya
more options

340MB

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

How many history items do you have if you type a colon in the search bar in the History Manager (Library)?

JEmlay
JEmlay Mai mallakar tambaya
more options

I just ran Places Maintenance v1.3 and that made it 348MB. Oops...

JEmlay
JEmlay Mai mallakar tambaya
more options

Where does it show a total count? If I try to highlight them all to get account FF just crashes.

JEmlay
JEmlay Mai mallakar tambaya
more options

After a few tries I was able to catch it saying 89,296. Then a message popped up saying:

A script on this page may be busy....

JEmlay
JEmlay Mai mallakar tambaya
more options

Zaɓi Mafita

So anyway....went ahead and blew out the history cache. I guess it'll just keep on happening as the history gets too large and there's no real fix for this.