/explore
|
You are here 
|
chriscoyier.net | ||
| | | | |
www.prepend.com
|
|
| | | | | I end up creating a bunch of j2ee apps that run on Oracle Application Server (OAS). When writing servlets/jsps it is frequently useful to get the URL or serv... | |
| | | | |
www.useragentman.com
|
|
| | | | | [AI summary] The blog post discusses accessibility coding best practices for web developers, offering open-source resources and community input. | |
| | | | |
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. | |
| | | | |
giuseppegurgone.com
|
|
| | | Engineering and thoughts. | ||
