I'm doing my best to ask this question, I'm stepping across domains here to cover for another team that is MIA on this task. Please guide me if the question sounds stupid.
We are dealing with a website that is reportedly hosted via VHost on Apache servers. So when we go to blah.oursite.com, many of our static assets actually come via redirect/proxy/something from a CDN that points to our S3 bucket.
So if I try to make a crude visual version of this: User > VHost site > redirect/proxy to CDN > S3
The site and assets for the VHost in this case (in the specific subdomain
blah) are protected by what we believe to be .htaccess controlled Basic HTTP password authentication. So when we visit blah.oursite.com we are presented by the browser with a popup requesting username and password. This is by design.
What we're seeing is that the few of our static assets that are hosted on an outside CDN are not able to be loaded on the
blah subdomain. If we load www.oursite.com then the assets all load without any problems. Therefore, one of our leading theories, as novices in this particular domain, is that the .htaccess credential protection is interfering with the
blah subdomain's ability to access the CDN'ed content.
Does that make any sense? Is that a possibility? What techniques might we use to test this theory (not knowing what sort of configurations are set by the team managing the Apache instances) or otherwise troubleshoot the issue? Are we out of luck without more cooperation from the other team?
I wish I could provide more detail on what is happening at the steps between
User > VHost site > redirect/proxy but unfortunately my team doesn't own those steps in the process and the team that does own them is not playing nicely with us on resolving this. Any help or hints to guide or help us find what the issue might be and how to resolve it would be super helpful; I have no experience with server administration.