Possibility to run cache warm up also with activated basic http auth

[aboritskiy]

Is your feature request related to a problem? Please describe. If production or staging env is behind basic http auth - cache warm up will fail cause it will not get access to the server. This makes it problematic to test if cache warm up actually works which preparing the website for go live without granting access to general public.

Describe the solution you'd like One can pass auth configuration to Guzzle Http lib, this way Guzzle will be able to authenticate against password protected magento pages and warm up cache.

Describe alternatives you've considered Possible alternative is simply always whitelist request coming from the host itself.

Additional context No additional context except for the fact that Guzzle Http actually supports that feature, one just needs to pass proper config in it.

[aboritskiy]

Possible alternative is simply always whitelist request coming from the host itself.

just tried that - it is not easy for the env that is behind Fastly, what will be the real container IP when it will hit the host? Is that container IP static? All those are shaky assumptions and better way is to allow passing basic http auth through.

[andriyShevtsov]

@aboritskiy is this request still up to date?

[aboritskiy]

@andriyShevtsov I think it is still up to date, as far as I know, cache warm up still breaks if website is behind basic auth.

[BaDos]

The internal task MCLOUD-9281 was created