Explore >> Select a destination
|
You are here 
|
blog.yadutaf.fr | ||
| | | | |
krasimirtsonev.com
|
|
| | | | | The simplest HTTP proxy with custom headers / These days I had an interesting problem to solve. At work, on our staging environment, we have basic authorization. It works really well but for some older versions of Chrome we experienced a weird issue. The browser did not pass the authorization header. The app runs fine but as soon as it does a fetch request to a local endpoint the request fails with 401 not-authorized error. In the modern browsers that's not happening because the browser kinda knows that we came here with basic auth and automatically includes authorization: basic ... header. | |
| | | | |
ponyfoo.com
|
|
| | | | | ||
| | | | |
jancat.github.io
|
|
| | | | | Node ?????JS ???????????????????????????????????????I/O ??"??"?????????????????? | |
| | | | |
philodev.one
|
|
| | | oAuth is a hard to get into because of its (necessary) complexity. A basic understanding of the standard flow and the actors involved can help to make better decisions and understand the security implications of the choices. | ||
