⚠ In case you've missed it, we have migrated to our new website, with a brand new forum. For more details about the migration you can read our blog post for website migration. This is an archived forum. ⚠

  •     

profile picture

Size of a request header field exceeds server limit.



Ocupado
  • profile picture
  • Member

Posted 05 October 2012 - 11:11 AM

Excellent library!... Very usefull to improve applications.

I am testing GroseryCrud with theme datatables. Then after six or more edit/add operations appears the following error:


[font=comic sans ms,cursive][i]Bad Request[/i][/font]

[font=comic sans ms,cursive][i]Your browser sent a request that this server could not understand.[/i][/font]
[font=comic sans ms,cursive][i]Size of a request header field exceeds server limit.[/i][/font]

[font=comic sans ms,cursive][i]Cookie[/i][/font]

I have tried some options to solve this issue:

1) I have downloaded at https://github.com/s.../zipball/master the version of saulimus where its available a fix to solve this problem. After install this version,the problem persists.

2) I made the changes to [i]datatables.js[/i] according to instructions contained in the post http://www.grocerycr...o-back-to-list/. I dont know if i did something wrong because the errors was not fixed after this.

3) The last option (not tested). I find out that is possible to increase the LimitRequestFieldSize parameter contained in http.conf o vhost.cfg files of apache. Due some recommendations i prefered not to test this option.

A question: I understand that this problem occurs only when datatables theme is used. If we use flexigrid the problem dissapears?


Thank,

Ocupado

Congrats! Exccelent piece of software

saulimus
  • profile picture
  • Member

Posted 05 October 2012 - 12:47 PM

Try removing all the cookies set by the site in your browser...

web-johnny
  • profile picture
  • Administrator
  • 1,166 posts

Posted 05 October 2012 - 14:29 PM

[member='Ocupado'] you don't have to download a fork for this. Just upgrade your grocery CRUD to the latest one 1.3.2 . This bug is already fixed.

Ocupado
  • profile picture
  • Member

Posted 05 October 2012 - 16:14 PM

Ok. I will do it.

Thanks,
Ocupado