The request record is too big

i get this in my error log:

2007/11/25 00:52:24 [alert] 14268#0: *17156 fastcgi: the request record
is
too big, client: 204.15.23.168, server: localhost, URL:
“/start?fb_sig_time=
1195951944.2615&fb_sig_added=1&fb_sig_session_key=f256886dd126f89dc72d9a6b-532559347&fb_sig_profile_update_time=1192712470&fb_sig_position_fix=0&fb_sig_user=532559347&fb_sig_expires=0&fb_sig=2868fb07f94b463f2d0950616094bbdf&fb_sig_api_key=d986f51fdd54acd4b26ccec75056aa25&fb_sig_friends=4711167%2C48300803%2C506840685%2C509158903%2C514282517%2C518501290%2C518751146%2C522135924%2C529596555%2C530467428%2C532045381%2C533925897%2C552413754%2C560512188%2C560918318%2C571236034%2C571560448%2C571655806%2C572481866%2C581388045%2C585140874%2C586256901%2C587180990%2C592871233%2C593017544%2C596111057%2C607812128%2C608338110%2C608648740%2C609136633%2C624457120%2C634132775%2C640874287%2C650661239%2C650663105%2C652620473%2C653611961%2C655450917%2C655731226%2C664067817%2C688266120%2C690980690%2C691471684%2C700335169%2C700576103%2C710666056%2C713512160%2C719541234%2C720808355%2C722805149%2C724561238%2C724607723%2C738516279%2C742985694%2C752953834%2C754068600%2C791348277%2C827690084&fb_sig_in_canvas=1”,
host: “x.x.x.x:8089”

does this mean this request is not getting served? is this a problem
with
nginx?
thanks a lot!

On Sam 24.11.2007 17:08, [email protected] wrote:

i get this in my error log:

2007/11/25 00:52:24 [alert] 14268#0: *17156 fastcgi: the request record is
too big, client: 204.15.23.168, server: localhost, URL: "

[snipp]

does this mean this request is not getting served? is this a problem
with nginx?

As Igor written in the mail thread

Re: upstream sent too big header

http://article.gmane.org/gmane.comp.web.nginx.english/1618


fastcgi_buffer_size 8k; # 16k, 32k, etc, until error will disappear.

Cheers && hth

Aleks

On Sat, Nov 24, 2007 at 05:08:00PM -0800, [email protected] wrote:

i get this in my error log:

2007/11/25 00:52:24 [alert] 14268#0: *17156 fastcgi: the request record is
too big, client: 204.15.23.168, server: localhost, URL: “/start?fb_sig_time=
1195951944.2615&fb_sig_added=1&fb_sig_session_key=f256886dd126f89dc72d9a6b-532559347&fb_sig_profile_update_time=1192712470&fb_sig_position_fix=0&fb_sig_user=532559347&fb_sig_expires=0&fb_sig=2868fb07f94b463f2d0950616094bbdf&fb_sig_api_key=d986f51fdd54acd4b26ccec75056aa25&fb_sig_friends=4711167%2C48300803%2C506840685%2C509158903%2C514282517%2C518501290%2C518751146%2C522135924%2C529596555%2C530467428%2C532045381%2C533925897%2C552413754%2C560512188%2C560918318%2C571236034%2C571560448%2C571655806%2C572481866%2C581388045%2C585140874%2C586256901%2C587180990%2C592871233%2C593017544%2C596111057%2C607812128%2C608338110%2C608648740%2C609136633%2C624457120%2C634132775%2C640874287%2C650661239%2C650663105%2C652620473%2C653611961%2C655450917%2C655731226%2C664067817%2C688266120%2C690980690%2C691471684%2C700335169%2C700576103%2C710666056%2C713512160%2C719541234%2C720808355%2C722805149%2C724561238%2C724607723%2C738516279%2C742985694%2C752953834%2C754068600%2C791348277%2C827690084&fb_sig_in_ca
nvas=1”,
host: “x.x.x.x:8089”

does this mean this request is not getting served? is this a problem with
nginx?

Yes, the request was not served.
nginx has one limitation: it sends client request header in the single
FastCGI record which maximum size is 64K. So this request header was
more
than 64K (URL or cookies).

On Son 25.11.2007 15:15, [email protected] wrote:

On Nov 25, 2007 12:11 AM, Aleksandar L. [email protected] wrote:

fastcgi_buffer_size 8k; # 16k, 32k, etc, until error will
disappear.

can you tell which file i can change this? i was not able to find it in
the source

http://wiki.codemongers.com/NginxHttpFcgiModule#fastcgi_buffer_size

maybe in the config file :wink:

Cheers

Aleks

fastcgi_buffer_size 8k; # 16k, 32k, etc, until error will disappear.
can you tell which file i can change this? i was not able to find it in
the
source
thanks

On Sat, Nov 24, 2007 at 05:08:00PM -0800, [email protected] wrote:

i get this in my error log:

2007/11/25 00:52:24 [alert] 14268#0: *17156 fastcgi: the request record is
too big, client: 204.15.23.168, server: localhost, URL: “/start?fb_sig_time=
1195951944.2615&fb_sig_added=1&fb_sig_session_key=f256886dd126f89dc72d9a6b-532559347&fb_sig_profile_update_time=1192712470&fb_sig_position_fix=0&fb_sig_user=532559347&fb_sig_expires=0&fb_sig=2868fb07f94b463f2d0950616094bbdf&fb_sig_api_key=d986f51fdd54acd4b26ccec75056aa25&fb_sig_friends=4711167%2C48300803%2C506840685%2C509158903%2C514282517%2C518501290%2C518751146%2C522135924%2C529596555%2C530467428%2C532045381%2C533925897%2C552413754%2C560512188%2C560918318%2C571236034%2C571560448%2C571655806%2C572481866%2C581388045%2C585140874%2C586256901%2C587180990%2C592871233%2C593017544%2C596111057%2C607812128%2C608338110%2C608648740%2C609136633%2C624457120%2C634132775%2C640874287%2C650661239%2C650663105%2C652620473%2C653611961%2C655450917%2C655731226%2C664067817%2C688266120%2C690980690%2C691471684%2C700335169%2C700576103%2C710666056%2C713512160%2C719541234%2C720808355%2C722805149%2C724561238%2C724607723%2C738516279%2C742985694%2C752953834%2C754068600%2C791348277%2C827690084&fb_sig_in_ca
nvas=1”,
host: “x.x.x.x:8089”

The attached patch should fix the bug.