Skip to content
This repository has been archived by the owner on Dec 24, 2023. It is now read-only.

Request Header Or Cookie Too Large #3

Open
anton-ko opened this issue Feb 22, 2015 · 1 comment
Open

Request Header Or Cookie Too Large #3

anton-ko opened this issue Feb 22, 2015 · 1 comment

Comments

@anton-ko
Copy link
Contributor

Apparently, the library saves way too much cookie data.

I am placing a call and checking the status of the call every second.
After a few calls I start getting this error and the only solution I've found is to manually clear the cache directory.

Wesnick\RingCentral\Exception\RingCentralException

Request Header Or Cookie Too Large

400 Bad Request

Request Header Or Cookie Too Large
nginx/1.2.3
(/home/vagrant/Code/app/protected/vendor/wesnick/ringcentral/src/Wesnick/RingCentral/RingOut.php:45)

Last time I've check cache file size was just over 31Kb

@wesnick
Copy link
Owner

wesnick commented Feb 27, 2015

I'm not sure how this could happen. Maybe you should subclass CookieJar and filter out uninteresting cookies. As I recall, the only cookie of interest is the auth cookie. At any rate, I developed this library but then never had the chance to use it in production as my client switched vendors so I don't really know how it works in the wild.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants