Unit test failure - get_query_string_parameters.should_return_decoded_paramter_values #1

poprhythm opened this Issue Feb 1, 2011 · 3 comments


None yet
2 participants

get_query_string_parameters.should_return_decoded_paramter_values : FailedSystem.ArgumentNullException: Value cannot be null.
Parameter name: str
at System.Security.Permissions.FileIOPermission.HasIllegalCharacters(String[] str)
at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList)
at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String path)
at System.Uri.ParseConfigFile(String file, ref IdnScopeFromConfig idnStateConfig, ref IriParsingFromConfig iriParsingConfig)
at System.Uri.GetConfig(ref UriIdnScope idnScope, ref Boolean iriParsing)
at System.Uri.InitializeUriConfig()
at System.Uri.InitializeUri(ParsingError err, UriKind uriKind, ref UriFormatException e)
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at OAuth.Web.Tests.OAuthWebRequestSignerSpecifications.get_query_string_parameters.should_return_decoded_paramter_values() in OAuthWebRequestSignerSpecifications.cs: line 381


buildmaster commented Feb 1, 2011

I'm not getting this failure locally, unsure how to fix as this seems to be a failure in URI constructor.

Did a little googling, and Ayende ran into the same issue - http://ayende.com/Blog/archive/2010/03/04/is-select-system.uri-broken.aspx - so, not a problem I suppose!


buildmaster commented Feb 2, 2011

yep, sounds like the same issue, I'll close this off.

Thanks again

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment