|
You are here |
www.prepend.com | ||
| | | | |
jaketrent.com
|
|
| | | | | If you don't see your HTTP response header in the browser, check your CORS policy. It's likely the culprit. | |
| | | | |
giuseppegurgone.com
|
|
| | | | | Engineering and thoughts. | |
| | | | |
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. | |
| | | | |
www.integralist.co.uk
|
|
| | | I've been learning Rust recently. This will probably be my third (lazy) attempt to learn the language. The reason I've failed previously is simply because I had no reason to learn it. Other than the memory safety aspects, which I like a lot, I don't actually like the design of the language at all (but that's a conversation for another day). This time around I want to learn the language as it's pertinent to my job. | ||