November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
November Happy Hour will be moved to Thursday December 5th.
"A potentially dangerous Request.Path" I think is from ASP.NET not from Epi.
Who consumes the API? You could add for example bearer token authentication or reqeust forgery protection or just filter input by some AntiXSS function.
Thanks Johan, It has been resolve. It's puplic page so can't used Bearer Token . Issue was default respose on 404 which include un decoded query string due to generic api route settings '
api/{controller}/{id}"
We have encoded the respose and clear the respose.
When using episerver with WebApi - it enable api controller for Reflected Cross site scripting (XSS) vulnerability.
When access resource via '/api/mycontroller/? <script>alert('hi');</script> '
result in
Reflected Cross site scripting (XSS) vulnerability. in response.
Note that the script tags are in the xml\JSON source.
If I drop the question mark, /api/mycontroller/. I'm getting correct HttpException.
Doesn it due to default Episerver routes configuration, is any way to prevent this? It's only happen when using webapi with Episerver
Default Route
Controller
[Pasting files is not allowed]