Shad Posted June 17, 2009 Share Posted June 17, 2009 Your search page isn't handling some search criteria too well, throwing back a stock IIS7 500 error. Seems to be on criteria less than 3 characters, or things like 4-1 which presumably are split down and then fail on length. Simon niknak.org Link to comment Share on other sites More sharing options...
Site Manager Posted June 17, 2009 Share Posted June 17, 2009 You're right! The previous OS actually gave a meaningful error message, I'll have to do something about it. I suspect that in this case it's because you fell foul of 'noise' words. The indexing strips out noise words to keep the database compact, and an error is thrown if a phrase that you are searching for only has noise words in it. I'll put a list on the search page so that they can be avoided. Link to comment Share on other sites More sharing options...
Shad Posted June 17, 2009 Author Share Posted June 17, 2009 Sounds good I had a nightmare recently after moving my site to IIS7. It has a very different handling of errors, particularly ones generated by code. In .NET3.5 they have introduced a special property 'HttpResponse.TrySkipIisCustomErrors' as a workaround, which did the trick for me. More info on that at http://www.west-wind.com/weblog/posts/745738.aspx if you're interested. Simon niknak.org Edited by - Shad on 17 Jun 2009 21:08:52 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now