Explore >> Select a destination
|
You are here 
|
www.pmatiello.me | ||
| | | | |
www.berkhanberkdemir.com
|
|
| | | | | ||
| | | | |
stribny.name
|
|
| | | | | ||
| | | | |
memo.mx
|
|
| | | | | Note This is a Work-In-Progress Document and the most up-to-date information is available at: github.com/memogarcia/openstack-deployer Deploying OpenStack using containers allows easy customisation and flexibility on how to deploy the platform for development, testing and production environments. Current deployment: stable/queens Host configuration The default configuration for this environment is composed by 3 main components that need to run on the host: Docker Libvirtd OpenVSwitch Docker will act as t... | |
| | | | |
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. | ||
