houbi56

Calling code: KeySegementTemplate.cs: 197 ODataUriUtils.ConvertFromUriLiteral(...)

Any updates on this? Seems like a rather serious bug!?

Any updates?

@KenitoInc Could the errand be reassigned or re-triaged? We're still affected by this bug.

@KenitoInc Great! Thanks for the feedback.

I see that the changes are merged. Is there an issue to track for the port to this repo?

There's a concurrency issue when using the EnableQueryAttribute since 7.5.4. See [https://github.com/OData/WebApi/issues/2390](https://github.com/OData/WebApi/issues/2390) It might be the culprit here as well.

@fubar-coder Any updates on the progress? Do you need any assistance?

That wont work though. The final output to the http body, written to by the FullDocumentResult, doesn't read from the loggingresponse's body memorystream.

A couple of idea's: The loggingwebdavresponse will always consume the body since the ContentType is hardcoded so the ` if (!RequestLogMiddleware.IsXml(ContentType)) { return null; }` will never be entered since...