More like this blocks particularly ones that have complex queries, especially with heavy node access rules can easily burst over the RFC 2616 200 byte limit
Attached patch forces solr queries to POST rather than GET to avoid this.
I've seen this issue has already been solved in the 6.x-3.x branch but the current stable 6.x release still has this issue, so submitting patch

Comments

Status: Needs review » Needs work

The last submitted patch, change_search_to_use_POSTS_instead_of_get.patch, failed testing.

chrisns’s picture

hopefully corrected patch file to pass automated tests

chrisns’s picture

Status: Needs work » Needs review
StatusFileSize
new1.07 KB

Status: Needs review » Needs work

The last submitted patch, change_search_to_use_POSTS_instead_of_get.patch, failed testing.

nick_vh’s picture

Drupal 6.x-1.x does not pass the tests unfortunately. No worries about that :)
Currently we can only enable/disable the testing functionality for the whole project. So we'll have to live with those red boxes for now

chrisns’s picture

Ah!
thanks Nick_vh for explaining that! :)

pwolanin’s picture

Version: 6.x-1.6 » 6.x-1.x-dev
Status: Needs work » Fixed

No, we already have this in 6.x-1.x in the Service class:

  public function search($query, $offset = 0, $limit = 10, $params = array(), $method = self::METHOD_GET) {
    if (!is_array($params)) {
      $params = array();
    }
...

    // Check string length of the query string, change method to POST
    // if longer than 4000 characters.
    if (strlen($queryString) > variable_get('apachesolr_search_post_threshold', 4000)) {
      $method = self::METHOD_POST;
    }

...

Please try adjusting that variable if your server is having issues.

Status: Fixed » Closed (fixed)

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