Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Are you using the released version of Content Delivery? This a known bug that should've been fixed.
Reposting this in correct room and description
Invalid non-ASCII or control character in header: 0x2212"
If you have multi-culture enabled and query delivery api in 'nb-no' culture whereas no issues for any other culture so far - but possibly could happen for other cultures i've only tried from a list of few
/api/episerver/v3.0/content/?contenturl=/nb-no/page-url/&expand=*
I started investigating this bit by bit and in the end it turns out the problem was coming from [OutputCacheFilterAttribute] when it tries to add etag hash-code (ETag hash contains non-ascii characters) in header like
typedHeaders.ETag = new EntityTagHeaderValue((StringSegment)("\"" + evaluateResult.ETag + "\""));
These are all private/seal classes methods so nothing much you can do to control it - any chance it can be base64 encoded before adding to header as .net 5 as of now does not seem to support non-ascii characters in header
Or any chance api can provide some options to control/disable etag generation? There is a ContentETagGenerator available but OutputCacheFilterAttribute re-generate hash again within its private methods.
Many thanks,
Kashif