ASP.NET MVC / Web API / Web Pageshttp://aspnetwebstack.codeplex.com/project/feeds/rssThis is the source code repository for open source ASP.NET products. The products include MVC, Web API and Web Pages with Razor.Edited Unassigned: ODataMediaTypeFormatter is throwing a SerializationException when SingleResult.Create takes in a query that returns an empty result. [2190]http://aspnetwebstack.codeplex.com/workitem/2190A SerializationException is being thrown from System.Web.OData.Formatter.ODataMediaTypeFormatter.GetSerializer(...) when SingleResult.Create(...) takes in a query that returns an empty result. <br /><br />This happens when an invalid key is specified by the user. A 404 Not Found should be returned instead of a 500 Internal Server Error.<br /><br />This issue is related to:<br />[https://aspnetwebstack.codeplex.com/workitem/1021](https://aspnetwebstack.codeplex.com/workitem/1021)<br />[https://aspnetwebstack.codeplex.com/workitem/1040](https://aspnetwebstack.codeplex.com/workitem/1040)<br /><br />__To Reproduce__<br />```<br />[EnableQuery]<br />public SingleResult<Product> GetProduct([FromODataUri] int key)<br />{<br /> return SingleResult.Create(Enumerable.Empty<Product>().AsQueryable());<br />}<br />```<br /><br /><br />__Exception Details__<br />```<br />{<br /> "message": "An error has occurred.",<br /> "innererror": {<br /> "message": "The 'ObjectContent`1' type failed to serialize the response body for content type 'application/json; odata.metadata=minimal'.",<br /> "type": "System.InvalidOperationException",<br /> "internalexception": {<br /> "message": "'SingleResult`1' cannot be serialized using the ODataMediaTypeFormatter.",<br /> "type": "System.Runtime.Serialization.SerializationException",<br /> "stacktrace": " at System.Web.OData.Formatter.ODataMediaTypeFormatter.GetSerializer(Type type, Object value, IEdmModel model, ODataSerializerProvider serializerProvider)\r\n at System.Web.OData.Formatter.ODataMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, HttpContent content, HttpContentHeaders contentHeaders)\r\n at System.Web.OData.Formatter.ODataMediaTypeFormatter.WriteToStreamAsync(Type type, Object value, Stream writeStream, HttpContent content, TransportContext transportContext, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.WebHost.HttpControllerHandler.<WriteBufferedResponseContentAsync>d__1b.MoveNext()"<br /> }<br /> }<br />}<br />```<br /><br />__Workaround__<br />```<br />public class NullSerializerProvider : DefaultODataSerializerProvider<br />{<br /> private readonly NullEntityTypeSerializer _nullEntityTypeSerializer;<br /><br /> public NullSerializerProvider()<br /> {<br /> _nullEntityTypeSerializer = new NullEntityTypeSerializer(this);<br /> }<br /><br /> public override ODataSerializer GetODataPayloadSerializer(IEdmModel model, Type type, HttpRequestMessage request)<br /> {<br /> var serializer = base.GetODataPayloadSerializer(model, type, request);<br /> if (serializer == null)<br /> {<br /> request.GetOwinContext().Response.StatusCode = (int)HttpStatusCode.NotFound;<br /> return _nullEntityTypeSerializer;<br /> }<br /> return serializer;<br /> }<br />}<br />```<br />```<br />public class NullEntityTypeSerializer : ODataEntityTypeSerializer<br />{<br /> public NullEntityTypeSerializer(ODataSerializerProvider serializerProvider)<br /> : base(serializerProvider)<br /> { }<br /><br /> public override void WriteObjectInline(object graph, IEdmTypeReference expectedType, ODataWriter writer, ODataSerializerContext writeContext)<br /> {<br /> if (graph != null)<br /> {<br /> base.WriteObjectInline(graph, expectedType, writer, writeContext);<br /> }<br /> }<br />}<br />```<br />```<br />var odataFormatters = ODataMediaTypeFormatters.Create(new NullSerializerProvider(), new DefaultODataDeserializerProvider());<br />config.Formatters.InsertRange(0, odataFormatters);<br />```<br />ryansimmenThu, 20 Nov 2014 15:48:11 GMTEdited Unassigned: ODataMediaTypeFormatter is throwing a SerializationException when SingleResult.Create takes in a query that returns an empty result. [2190] 20141120034811PCreated Unassigned: ODataMediaTypeFormatter is throwing a SerializationException when SingleResult.Create takes in a query that returns an empty result. [2190]http://aspnetwebstack.codeplex.com/workitem/2190A SerializationException is being thrown from System.Web.OData.Formatter.ODataMediaTypeFormatter.GetSerializer(...) when SingleResult.Create(...) takes in a query that returns an empty result. <br /><br />This happens when an invalid key is specified by the user. A 404 Not Found should be returned instead of a 500 Internal Server Error.<br /><br />This issue is related to:<br />[https://aspnetwebstack.codeplex.com/workitem/1021](http://www.example.com)<br />[https://aspnetwebstack.codeplex.com/workitem/1040](http://www.example.com)<br /><br />__To Reproduce__<br />```<br />[EnableQuery]<br />public SingleResult<Product> GetProduct([FromODataUri] int key)<br />{<br /> return SingleResult.Create(Enumerable.Empty<Product>().AsQueryable());<br />}<br />```<br /><br /><br />__Exception Details__<br />```<br />{<br /> "message": "An error has occurred.",<br /> "innererror": {<br /> "message": "The 'ObjectContent`1' type failed to serialize the response body for content type 'application/json; odata.metadata=minimal'.",<br /> "type": "System.InvalidOperationException",<br /> "internalexception": {<br /> "message": "'SingleResult`1' cannot be serialized using the ODataMediaTypeFormatter.",<br /> "type": "System.Runtime.Serialization.SerializationException",<br /> "stacktrace": " at System.Web.OData.Formatter.ODataMediaTypeFormatter.GetSerializer(Type type, Object value, IEdmModel model, ODataSerializerProvider serializerProvider)\r\n at System.Web.OData.Formatter.ODataMediaTypeFormatter.WriteToStream(Type type, Object value, Stream writeStream, HttpContent content, HttpContentHeaders contentHeaders)\r\n at System.Web.OData.Formatter.ODataMediaTypeFormatter.WriteToStreamAsync(Type type, Object value, Stream writeStream, HttpContent content, TransportContext transportContext, CancellationToken cancellationToken)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.WebHost.HttpControllerHandler.<WriteBufferedResponseContentAsync>d__1b.MoveNext()"<br /> }<br /> }<br />}<br />```<br /><br />__Workaround__<br />```<br />public class NullSerializerProvider : DefaultODataSerializerProvider<br />{<br /> private readonly NullEntityTypeSerializer _nullEntityTypeSerializer;<br /><br /> public NullSerializerProvider()<br /> {<br /> _nullEntityTypeSerializer = new NullEntityTypeSerializer(this);<br /> }<br /><br /> public override ODataSerializer GetODataPayloadSerializer(IEdmModel model, Type type, HttpRequestMessage request)<br /> {<br /> var serializer = base.GetODataPayloadSerializer(model, type, request);<br /> if (serializer == null)<br /> {<br /> request.GetOwinContext().Response.StatusCode = (int)HttpStatusCode.NotFound;<br /> return _nullEntityTypeSerializer;<br /> }<br /> return serializer;<br /> }<br />}<br />```<br />```<br />public class NullEntityTypeSerializer : ODataEntityTypeSerializer<br />{<br /> public NullEntityTypeSerializer(ODataSerializerProvider serializerProvider)<br /> : base(serializerProvider)<br /> { }<br /><br /> public override void WriteObjectInline(object graph, IEdmTypeReference expectedType, ODataWriter writer, ODataSerializerContext writeContext)<br /> {<br /> if (graph != null)<br /> {<br /> base.WriteObjectInline(graph, expectedType, writer, writeContext);<br /> }<br /> }<br />}<br />```<br />```<br />var odataFormatters = ODataMediaTypeFormatters.Create(new NullSerializerProvider(), new DefaultODataDeserializerProvider());<br />config.Formatters.InsertRange(0, odataFormatters);<br />```<br />ryansimmenThu, 20 Nov 2014 15:00:17 GMTCreated Unassigned: ODataMediaTypeFormatter is throwing a SerializationException when SingleResult.Create takes in a query that returns an empty result. [2190] 20141120030017PNew Post: Where is Web API Help Page 5.2.2 nuget packet source code ?http://aspnetwebstack.codeplex.com/discussions/572603<div style="line-height: normal;">When browsing the master and the different branches on codeplex I can see that the current version is 5.1.0-alpha-0 but yet on nuget we have a 5.2.2 version of the package...I can't understand where it comes from :)<br />
</div>sigomatixThu, 20 Nov 2014 10:19:19 GMTNew Post: Where is Web API Help Page 5.2.2 nuget packet source code ? 20141120101919ANew Post: Where is Web API Help Page 5.2.2 nuget packet source code ?http://aspnetwebstack.codeplex.com/discussions/572603<div style="line-height: normal;">When browsing the master and the different branches on codeplex I can see that the current version is 5.1.0-alpha-0 but yet on nuget we have a 5.2.2 version of the package...I can't understand where it comes from :)<br />
</div>sigomatixThu, 20 Nov 2014 10:19:19 GMTNew Post: Where is Web API Help Page 5.2.2 nuget packet source code ? 20141120101919ANew Post: Where is Web API Help Page 5.2.2 nuget packet source code ?http://aspnetwebstack.codeplex.com/discussions/572603<div style="line-height: normal;">When browsing the master and the different branches on codeplex I can see that the current version is 5.1.0-alpha-0 but yet on nuget we have a 5.2.2 version of the package...I can't understand where it comes from :)<br />
</div>sigomatixThu, 20 Nov 2014 10:19:19 GMTNew Post: Where is Web API Help Page 5.2.2 nuget packet source code ? 20141120101919ACommented Feature: Enum on un-type support [1956]http://aspnetwebstack.codeplex.com/workitem/1956Currently, enum on un-type doesn't work. While, the collection of enum on un-type doesn't work too. <br /><br />As ODL spec says:<br /><br />Structural property can be :<br />1) primitive type<br />2) complex type<br />3) enum type<br />4) the collection of the above.<br /><br />So. Please add the support enum on un-type.<br /><br />Comments: Similar to: https://aspnetwebstack.codeplex.com/workitem/2186 xuzhgThu, 20 Nov 2014 03:28:47 GMTCommented Feature: Enum on un-type support [1956] 20141120032847ACommented Unassigned: Deserialization of untyped enums and serialization of collection of untyped enum collection fails [2186]http://aspnetwebstack.codeplex.com/workitem/2186Hi Team,<br /><br />I am working with Odata v4.0 and ASP Web API 2.2.<br /><br />while I was working on EdmOperations I encountered issues with untyped enums.<br /><br />All the parameter types added to operations are untyped(Both request and response parameters).<br /><br />When tried to invoke operation which takes enum as a parameter ,the Enum deserialization failed and the exception message is "Value cannot be null"<br /><br />When investigated I found that the OdataEnumSerializer tried to get the Clr type of enum from internal cache and it failed in getting so.<br /><br />Similarly while returning the Collection of Untyped enums in response, the OdataCollectionSerializer failed to deserialize since it could not find the appropriate clr type in internal cache.<br /><br />Could you guys investigate further and help me with the fix for these issues ?<br /><br />Thank you,<br />Kedarnath K<br />Comments: It seems duplicated with https://aspnetwebstack.codeplex.com/workitem/1956 xuzhgThu, 20 Nov 2014 03:26:43 GMTCommented Unassigned: Deserialization of untyped enums and serialization of collection of untyped enum collection fails [2186] 20141120032643AEdited Unassigned: Deserialization of untyped enums and serialization of collection of untyped enum collection fails [2186]http://aspnetwebstack.codeplex.com/workitem/2186Hi Team,<br /><br />I am working with Odata v4.0 and ASP Web API 2.2.<br /><br />while I was working on EdmOperations I encountered issues with untyped enums.<br /><br />All the parameter types added to operations are untyped(Both request and response parameters).<br /><br />When tried to invoke operation which takes enum as a parameter ,the Enum deserialization failed and the exception message is "Value cannot be null"<br /><br />When investigated I found that the OdataEnumSerializer tried to get the Clr type of enum from internal cache and it failed in getting so.<br /><br />Similarly while returning the Collection of Untyped enums in response, the OdataCollectionSerializer failed to deserialize since it could not find the appropriate clr type in internal cache.<br /><br />Could you guys investigate further and help me with the fix for these issues ?<br /><br />Thank you,<br />Kedarnath K<br />xuzhgThu, 20 Nov 2014 03:26:43 GMTEdited Unassigned: Deserialization of untyped enums and serialization of collection of untyped enum collection fails [2186] 20141120032643AReviewed: v5.3 RTM (十一月 18, 2014)https://aspnetwebstack.codeplex.com/releases/view/134124#ReviewBy-DanielCullenRated 4 Stars (out of 5) - i'll see thisDanielCullenWed, 19 Nov 2014 02:22:00 GMTReviewed: v5.3 RTM (十一月 18, 2014) 20141119022200ACommented Feature: OData V4 service should support DateTime [2072]http://aspnetwebstack.codeplex.com/workitem/2072OData V4 should support DateTime or you should give the developer a way of converting datatime to datetimeoffset when the service is called.<br />I have several serializable objects that are in 3rd party libraries (even Microsoft core classes) that have datatime properties that will not be exposable through OData V4 services.<br /><br />here is OASIS meeting showing that Edm.DateTime was discussed as adding back but then was "defer this to a future version"?<br />https://issues.oasis-open.org/browse/ODATA-220<br /><br /><br /><br />Comments: Based on https://issues.oasis-open.org/browse/ODATA-220 the issue is being "DEFERRED" until "V5.0". Wonder when "V5.0" is going to be released so that we can use OData again? gorothTue, 18 Nov 2014 21:19:32 GMTCommented Feature: OData V4 service should support DateTime [2072] 20141118091932PCreated Unassigned: Web API 2.2 Thread.CurrentPrincipal and HttpContext.Current.User not in sync [2189]http://aspnetwebstack.codeplex.com/workitem/2189Principal's Identity is being changed during same Http request.<br />Thread.CurrentPrincipal and HttpContext.Current.User held correctly new value until the very end of WebAPI method action.<br />OnActionExecuted filter action Thread.CurrentPrincipal is reverted to previous value and no longer in sync with System.Web.HttpContext.Current.User (which still holds correct value).<br /><br />This started to happen only after upgrade to Web API 2.2.<br />jovanaTue, 18 Nov 2014 15:33:44 GMTCreated Unassigned: Web API 2.2 Thread.CurrentPrincipal and HttpContext.Current.User not in sync [2189] 20141118033344PCommented Feature: OData V4 service should support DateTime [2072]http://aspnetwebstack.codeplex.com/workitem/2072OData V4 should support DateTime or you should give the developer a way of converting datatime to datetimeoffset when the service is called.<br />I have several serializable objects that are in 3rd party libraries (even Microsoft core classes) that have datatime properties that will not be exposable through OData V4 services.<br /><br />here is OASIS meeting showing that Edm.DateTime was discussed as adding back but then was "defer this to a future version"?<br />https://issues.oasis-open.org/browse/ODATA-220<br /><br /><br /><br />Comments: As to what I wrote earlier about the 2 workarounds from http://stackoverflow.com/questions/25189557/how-to-get-web-api-odata-v4-to-use-datetime http://damienbod.wordpress.com/2014/06/16/web-api-and-odata-v4-crud-and-actions-part-3/ neither work. You can no longer filter or sort by these fields or get this error http://localhost:18832/Aas/Activities?$top=11&$orderby=CreatedAt Gives this error "code":"","message":"An error has occurred.","innererror":{ "message":"The 'ObjectContent`1' type failed to serialize the response body for content type 'application/json; odata.metadata=minimal'.","type":"System.InvalidOperationException","stacktrace":"","internalexception":{ "message":"The specified type member 'CreatedAt' is not supported in LINQ to Entities. Only initializers, entity members, and entity navigation properties are supported.","type":"System.NotSupportedException","stacktrace":" But this works as it is addressed indirectly http://localhost:18832/Aas/AppUsers%28102%29/AppUserActivities?$expand=Case&$filter=%28Reminder%20ne%20null%20and%20IsComplete%20eq%20null%29&$top=15&$orderby=Reminder&$count=true Reminder Iscomplete are from activity from AppUserActivities. This is wierd. Does anyone have a solution? I connect to mysql. You bunch of idiots. There is not a datetimeoffset. And everyone wonders why no one wants to develop for Microsoft Technologies. jonagostinelloMon, 17 Nov 2014 23:11:36 GMTCommented Feature: OData V4 service should support DateTime [2072] 20141117111136PCommented Feature: Support CRUD on single dynamic property of open type [1942]http://aspnetwebstack.codeplex.com/workitem/1942Do we want to support CRUD on single dynamic property of the open type?<br /><br />for example:<br /><br />Get ~/Customers(1)/MyDynamicPropertName<br /><br />Post ~/Customers(1)/MyDynamicPropertName<br /><br />Put ~/Customers(1)/MyDynamicPropertName<br /><br />Patch ~/Customers(1)/MyDynamicPropertName<br /><br />Delete ~/Customers(1)/MyDynamicPropertName<br />Comments: Also, it would be nice if the AttributeRoutingConvention provided a mechanism for matching dynamic properties generically. E.g. [ODataRoute("/MyEntitySet/{key}/{propertyName}] public IHttpActionResult GetProperty([FromODataUrl] string key, string propertyName) { ... }ificatorMon, 17 Nov 2014 20:56:17 GMTCommented Feature: Support CRUD on single dynamic property of open type [1942] 20141117085617PClosed Unassigned: WebAPI 2: "Authorization: Bearer <token>" fails under IIS [2177]http://aspnetwebstack.codeplex.com/workitem/2177We had a build issue last week that forced us to update all of the NuGet packages to the current published release version on 10/29/2014. This build appears to have broken the use of bearer tokens in the web request, but only when the OWIN application is running under IIS. It works fine as an OWIN hosted Windows Service, and cookie authentication works in both environments. The response from IIS when using bearer authentication ("Authorization: Bearer <token>") is:<br /><br />```<br />{<br /> "message": "An error has occurred.",<br /> "exceptionMessage": "Sequence contains more than one element",<br /> "exceptionType": "System.InvalidOperationException",<br /> "stackTrace": " at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)\r\n at Microsoft.Owin.Security.AuthenticationManager.<AuthenticateAsync>d__8.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n at System.Web.Http.HostAuthenticationFilter.<AuthenticateAsync>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.AuthenticationFilterResult.<ExecuteAsync>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()"<br />}<br />```<br />If we remove the "Authorization" header and just use cookie authentication, IIS will again work. Prior to the NuGet package upgrades the "Authorization" header worked as well, so something in the latest packages is causing it to fail.<br /><br />Easier to read stack trace:<br />```<br /> at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)<br /> at Microsoft.Owin.Security.AuthenticationManager.<AuthenticateAsync>d__8.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()<br /> at System.Web.Http.HostAuthenticationFilter.<AuthenticateAsync>d__0.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Web.Http.Controllers.AuthenticationFilterResult.<ExecuteAsync>d__0.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()<br /> at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()<br />```<br />yishaigalatzerMon, 17 Nov 2014 20:37:26 GMTClosed Unassigned: WebAPI 2: "Authorization: Bearer <token>" fails under IIS [2177] 20141117083726PCommented Unassigned: WebAPI 2: "Authorization: Bearer <token>" fails under IIS [2177]http://aspnetwebstack.codeplex.com/workitem/2177We had a build issue last week that forced us to update all of the NuGet packages to the current published release version on 10/29/2014. This build appears to have broken the use of bearer tokens in the web request, but only when the OWIN application is running under IIS. It works fine as an OWIN hosted Windows Service, and cookie authentication works in both environments. The response from IIS when using bearer authentication ("Authorization: Bearer <token>") is:<br /><br />```<br />{<br /> "message": "An error has occurred.",<br /> "exceptionMessage": "Sequence contains more than one element",<br /> "exceptionType": "System.InvalidOperationException",<br /> "stackTrace": " at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)\r\n at Microsoft.Owin.Security.AuthenticationManager.<AuthenticateAsync>d__8.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n at System.Web.Http.HostAuthenticationFilter.<AuthenticateAsync>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.AuthenticationFilterResult.<ExecuteAsync>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()"<br />}<br />```<br />If we remove the "Authorization" header and just use cookie authentication, IIS will again work. Prior to the NuGet package upgrades the "Authorization" header worked as well, so something in the latest packages is causing it to fail.<br /><br />Easier to read stack trace:<br />```<br /> at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source)<br /> at Microsoft.Owin.Security.AuthenticationManager.<AuthenticateAsync>d__8.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()<br /> at System.Web.Http.HostAuthenticationFilter.<AuthenticateAsync>d__0.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Web.Http.Controllers.AuthenticationFilterResult.<ExecuteAsync>d__0.MoveNext()<br />--- End of stack trace from previous location where exception was thrown ---<br /> at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)<br /> at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()<br /> at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext()<br />```<br />Comments: @Kaelum thanks for your feedback. We are going to close this, as the fact that something that is not supported "sometimes" work is not expected but nothing warranting a fix,yishaigalatzerMon, 17 Nov 2014 20:37:20 GMTCommented Unassigned: WebAPI 2: "Authorization: Bearer <token>" fails under IIS [2177] 20141117083720PEdited Unassigned: Odata+WebApi Filtering Open Dynamic Objects. SingleValueOpenPropertyAccess. [2187]http://aspnetwebstack.codeplex.com/workitem/2187I am attempting to apply an Odataquery against a collection of Json objects (OpenType / Dynamic). I have instantiated my json as "MyDynamicObjects", a class which simply enumerates each json property in a DynamicProperties dictionary (as demonstrated in the opentype samples).<br /><br />```<br /> public class MyDynamicObject : Dictionary<string, object><br /> {<br /> public IDictionary<string, object> DynamicProperties<br /> {<br /> get { return this; }<br /> } <br /> }<br />```<br /><br />I am serving this object via a WebApi controller.<br /><br />```<br /> [EnableQuery(PageSize = 25, MaxExpansionDepth = 5)]<br /> public IQueryable Get(ODataQueryOptions<MyDynamicObject> options)<br /> {<br /> return MyRepository.AsQueryable();<br /> }<br />```<br /><br />The method works fine so long as I do not attempt to filter my data. When I attempt to filter my data, it dies.<br /><br />```<br /> "Message": "The query specified in the URI is not valid. Validating OData QueryNode of kind SingleValueOpenPropertyAccess is not supported by FilterQueryValidator.",<br /> "ExceptionMessage": "Validating OData QueryNode of kind SingleValueOpenPropertyAccess is not supported by FilterQueryValidator.",<br /> "ExceptionType": "System.NotSupportedException",<br /> "StackTrace": " at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateSingleValueNode(SingleValueNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateQueryNode(QueryNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateConvertNode(ConvertNode convertNode, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateSingleValueNode(SingleValueNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateQueryNode(QueryNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateLogicalOperator(BinaryOperatorNode binaryNode, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateBinaryOperatorNode(BinaryOperatorNode binaryOperatorNode, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateSingleValueNode(SingleValueNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.ValidateQueryNode(QueryNode node, ODataValidationSettings settings)<br /> at System.Web.OData.Query.Validators.FilterQueryValidator.Validate(FilterQueryOption filterQueryOption, ODataValidationSettings settings)<br /> at System.Web.OData.Query.FilterQueryOption.Validate(ODataValidationSettings validationSettings)\r\n at System.Web.OData.Query.Validators.ODataQueryValidator.Validate(ODataQueryOptions options, ODataValidationSettings validationSettings)<br /> at System.Web.OData.Query.ODataQueryOptions.Validate(ODataValidationSettings validationSettings)\r\n at System.Web.OData.EnableQueryAttribute.ValidateQuery(HttpRequestMessage request, ODataQueryOptions queryOptions)<br /> at System.Web.OData.EnableQueryAttribute.ExecuteQuery(Object response, HttpRequestMessage request, HttpActionDescriptor actionDescriptor)<br /> at System.Web.OData.EnableQueryAttribute.OnActionExecuted(HttpActionExecutedContext actionExecutedContext)"<br /><br />```<br /><br />I am not sure how to proceed. Is Filtering even supported ? If not when is it scheduled to be supported. <br /><br />Lastly, I have tried other ways of going about this such as returning a newtonsoft JObject and calling the Apply method myself. <br />yishaigalatzerMon, 17 Nov 2014 20:35:25 GMTEdited Unassigned: Odata+WebApi Filtering Open Dynamic Objects. SingleValueOpenPropertyAccess. [2187] 20141117083525PClosed Unassigned: Microsoft.Web.Infrastructure was published in Debug mode [2170]http://aspnetwebstack.codeplex.com/workitem/2170Could Microsoft publish a Release version of Microsoft.Web.Infrastructure ?<br /><br />Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35: has debug flags Default, IgnoreSymbolStoreSequencePoints<br /><br />It is causing debugger pop-ups on our production server for w3wp.exe and causes the site to freeze.<br /><br />The file was provided as package on nuget (Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL) and also as part of a MVC installation C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v2.0\Assemblies\Microsoft.Web.Infrastructure.dll. File and product version is 1.0.20105.407.<br /><br />Thanks,<br /><br />Willem-Derk.<br />yishaigalatzerMon, 17 Nov 2014 20:34:36 GMTClosed Unassigned: Microsoft.Web.Infrastructure was published in Debug mode [2170] 20141117083436PCommented Unassigned: Microsoft.Web.Infrastructure was published in Debug mode [2170]http://aspnetwebstack.codeplex.com/workitem/2170Could Microsoft publish a Release version of Microsoft.Web.Infrastructure ?<br /><br />Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35: has debug flags Default, IgnoreSymbolStoreSequencePoints<br /><br />It is causing debugger pop-ups on our production server for w3wp.exe and causes the site to freeze.<br /><br />The file was provided as package on nuget (Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL) and also as part of a MVC installation C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v2.0\Assemblies\Microsoft.Web.Infrastructure.dll. File and product version is 1.0.20105.407.<br /><br />Thanks,<br /><br />Willem-Derk.<br />Comments: Thanks for replying. Unfortunately we have no other repro scenario for this. And after discussing with the author of this code we don't believe there is a strong enough reason to reship a new version in release mode. This is one of the most popular packages on nuget for several years, and this is the only feedback we heard so far on this matter. So without any more feedback I am going to close this as won't fix. If you can provide a dump please reopen and we will take another look.yishaigalatzerMon, 17 Nov 2014 20:34:30 GMTCommented Unassigned: Microsoft.Web.Infrastructure was published in Debug mode [2170] 20141117083430PEdited Issue: Client-side validation appends aria-required for every error [2139]http://aspnetwebstack.codeplex.com/workitem/2139Whether this is an error in the adapter or the jQuery Validation framework I am unsure about.<br />Maybe it is even the desired behaviour? But it seems quite weird to me.<br /><br />Every time an error is triggered (onkeyup) and you have clientside validation running using an attribute (haven' tested manually hooking it up), it will append a value to the aria-required attribute.<br /><br />For an example your input can end up looking like this<br /><br /><input autocomplete="off" data-val="true" data-val-email="The Indtast e-mail field is not a valid e-mail address." data-val-required="The Indtast e-mail field is required." id="GasOrElectric_EmailLookup_Email" name="GasOrElectric.EmailLookup.Email" type="text" value="" aria-required="true" aria-invalid="false" aria-describedby="GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error GasOrElectric_EmailLookup_Email-error" class="valid"><br /><br />To me it seems adding it one time would be enough.<br />yishaigalatzerMon, 17 Nov 2014 20:27:04 GMTEdited Issue: Client-side validation appends aria-required for every error [2139] 20141117082704PEdited Issue: Misleading Behavior: There is no way to pass the UseViewData property when creating a HiddenFor. [2146]http://aspnetwebstack.codeplex.com/workitem/2146As it stands today, when creating a HiddenFor() on a view the HTMLHelper will automatically pass __FALSE__ for the UseViewData property on the InputHelper() Method. <br /><br />Shown Here:<br />```<br />public static MvcHtmlString HiddenFor<TModel, TProperty>(this HtmlHelper<TModel> htmlHelper, Expression<Func<TModel, TProperty>> expression, IDictionary<string, object> htmlAttributes)<br /> {<br /> ModelMetadata metadata = ModelMetadata.FromLambdaExpression(expression, htmlHelper.ViewData);<br /> return HiddenHelper(htmlHelper, metadata, metadata.Model, false, ExpressionHelper.GetExpressionText(expression), htmlAttributes);<br /> }<br />```<br /><br />This can be misleading to developers as it will try and read values from the ModelState first, then from the Model if nothing is found. <br /><br />If developers have the ability to pass the UseViewData value while creating a HiddenFor(), then we can bypass reading values directly from ModelState.<br /><br />Suggestion:<br />Create an overload for HiddenFor() to accept the passing of UseViewData Property.<br /><br />__OR__<br /><br />At least, update your documentation for the HTMLHelper methods to include details on the default nature of reading from ModelState.<br /><br /><br />To clarify WHY this is an issue:<br /><br />When having a querystring property of the same name as a property in your model any HiddenFor() helpers bound to that property will take the value of the querystring over the model automatically. __I assume this is probably by design but the developer should at least be made aware of this behavior.__ <br />yishaigalatzerMon, 17 Nov 2014 20:26:41 GMTEdited Issue: Misleading Behavior: There is no way to pass the UseViewData property when creating a HiddenFor. [2146] 20141117082641P