You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If blink1-tiny-server is started with --no-html and an unrecognized uri is requested (eg: /404), then the requests is never completed.
Note that echoing the requested uri back to the client (like was done before version 2.3.0) could open up an XSS, so either don't echo the uri back in the response, or ensure that it is appropriately encoded and that correct http response header (Content-type: application/json? X-Content-Type-Options: nosniff?) is set to ensure that browsers interpret the response as json.
The text was updated successfully, but these errors were encountered:
- handle unknown URIs in /blink/*
- explicitly set headers content-type application/json and x-content-type-options nosniff
- remove potential XSS vector of echoing uri in JSON response
- removed list of URIs in /blink1 status message as it created bad json
If blink1-tiny-server is started with
--no-html
and an unrecognized uri is requested (eg: /404), then the requests is never completed.Note that echoing the requested uri back to the client (like was done before version 2.3.0) could open up an XSS, so either don't echo the uri back in the response, or ensure that it is appropriately encoded and that correct http response header (
Content-type: application/json
?X-Content-Type-Options: nosniff
?) is set to ensure that browsers interpret the response as json.The text was updated successfully, but these errors were encountered: