Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
I forgot to mention that the site is an internal intranet site where users are always logged on (through integrated authentication).
Stack-trace;
System.Uri.UnescapeString(Char* pStr, Int32 start, Int32 end, Char[] dest, Int32& destPosition, Char rsvd1, Char rsvd2, Char rsvd3, UnescapeMode unescapeMode, UriParser syntax, Boolean isQuery, Boolean readOnlyConfig) +1197
Hi,
This is registered bug which has been fixed in SP3
Bug #10555: Querystring with åäö crashes page if friendlyurl is enabled
Possible Workaround:
Do you have a file named: EPiServerLog.config in your site root? If you have, and that file contains a root logger on <level value="debug" />, change that to <level value="error" /> your page will not crash anymore.
Thank you!! Logging error messages only solved it.
I thought I was going crazy because I've seen the error appear and disappear w/o any real explanation =)
Hi,
I'm getting a .net yellow page when I'm doing a redirect to a page with åäö in the URL. It's a simple search form where users enter a search phrase into a text box. When the user submits the form I create a URL to the search listing page. The contents in the form is URLEncoded before redirecting.
But on the search result-page I get a .net-error:
"Invalid URI: There is an invalid sequence in the string.
Exception Details: System.UriFormatException: Invalid URI: There is an invalid sequence in the string."
The URL looks something like this:
"http:///Sokresultat/?ph=S%c3%b6k+Person&searchtype=person"
The phrase searched is "Sök Person", but all texts with åäö cause the same problem.
I'm running EPiServer 5.1.422.256. Any ideas what might cause the problem?
Regards,
Peter