Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

General Questions

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, biapar, Willr, Ingo, swaiba, simon_w

Request URI Too Large When Linking DataObjects To Page


6 Posts   708 Views


15 November 2012 at 8:14am Community Member, 470 Posts

I have a dataobject that I'm trying to link to a page, but it fails on certain pages that have a lot of content and custom fields with error 414 Request URI Too Large.

I can add new dataobjects but it's when I want to link an existing one to a page that the search fails.

When I look through Chrome's console, I see the request URL takes all the content/fields and puts in the url:

So for small pages it works fine because the URL stays small, but if you have a content heavy page, this fails.

Is this a known bug or is there a work around?


15 November 2012 at 10:00am Forum Moderator, 921 Posts

So all the fields have their content entered into the URL? That seems like a bug to me, especially if there's a 414 error.

Which component are you using to search getting the failing request?



15 November 2012 at 12:48pm (Last edited: 15 November 2012 12:50pm), Community Member, 470 Posts

I did a search and it happens to this person too

I'm using gridfield with a many_many relationship.

Here is the screenshot of console

This happens when I try searching existing dataobjects to link to the page.

I am using a multilingual module, so you'll see translation fields there, but it happens with regular dataobjects too, so it's not that module.


20 November 2012 at 8:34am Community Member, 470 Posts

Should I open a ticket for this? I don't know enough about the framework but it seems like this is done on purpose, but fails if you have large content. I'm not the only one getting this.


8 April 2013 at 3:16am Community Member, 51 Posts

Hi mate, did you found a solution for this issue?


8 April 2013 at 3:21am Community Member, 470 Posts

No, I just left it out for the time being as the site I was working on didn't absolutely need it. I was just waiting for a fix.