Magnus Rahl
Feb 21, 2011
  3208
(1 votes)

Search Service problem for users with many groups

The new EPiServer Full Text Search is fully integrated into the RelatePlus package. All content created is added to the search index, including the content’s access rights. That means access control filtering can be done by the indexing service before returning search result. Very convenient for paging of results etc. when you know you can display all the results returned.

Unexpected limitations

Suddenly some of our users didn’t get any search results back. Digging in the log showed several errors and after repeating the queries I could see that they returned 404 not found even though other queries worked perfectly.

After further troubleshooting it was evident that it was the length of the query (which is passed to the REST service in the query string) that was the culprit. Since the user’s groups are passed to the indexing service, a user with many groups performing a search will result in a very long query string.

Since, at least in the RelatePlus standard templates, users are added to a new group for each Club they join the query can grow large very fast.  If you have built your community based on the RelatePlus templates you could have users who are unable to perform searches.

Solution

ASP.NET has a setting for the maximum allowed length of the QueryString (note that this is a server to server call, so no browsers are involved, but they also have limitations). This is set in the configuration / system.webServer / security / requestFiltering / requestLimits elements in the maxQueryString attribute. There is also a maxUrl attribute but they are independent (maxUrl is everything up to the query, but not including it). De default value for maxQueryString if it is not set is 2048, which was the limit my users’ queries hit. I simply increased this value like so:

<system.webServer>
  <security>
    <requestFiltering>
      <requestLimits maxQueryString="16384" />
    </requestFiltering>
  </security>
</system.webServer>
Feb 21, 2011

Comments

Nov 23, 2011 05:38 PM

And if you are running ASP.NET 4 you also need to set the new maxQueryStringLength on the httpRuntime element.

Please login to comment.
Latest blogs
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously smtp.episerver.net was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog