Hi,

I'm getting this error on our server when I'm trying to click on pager buttons during browsing content in the nodeexplorer modal window:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.<br /> </p> </body></html>

All view pager buttons sending too big GET HTTP requests. I captured several requests and it seems that parameter "view_args" in the GET requests contains all node IDs which can be chosen with nodereference explorer. In our case with around 2000 referenced nodes we get more than 11.000 characters/bytes long URL which is rejected by Apache.

We tried to setup Apache server to accept longer URLs but we didn't succeed. Further information: http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestline

Anyway Internet Explorer has URL own length limit set to 2083 characters, so longer URL's will not work on all IE until IE8. Read http://support.microsoft.com/kb/208427/en-us

CommentFileSizeAuthor
#1 nodereference_explorer.views_.class_.inc_625474_views_pager_20091109.patch6.11 KBgnindl

Comments

gnindl’s picture

gnindl commented
Assigned: Unassigned » gnindl
Status: Active » Fixed
StatusFileSize
new nodereference_explorer.views_.class_.inc_625474_views_pager_20091109.patch6.11 KB

I assume you are using the default view for nodereference explorer?

Nodes are now filtered by their type rather than setting all possible node ids into the url

meba’s picture

meba commented

I don't really think this fixed that. The explorer doesn't work at all now, showing two views in one. using beta7

gnindl’s picture

gnindl commented

That's another issue, probably one of those two:

http://drupal.org/node/564882

http://drupal.org/node/578402

I have tested this widget on Firefox 3/3.5 and IE 8. In other browser it may break.

The long request query issue is solved with this patch. It didn't touch any JS here.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.