Just a thought - have you tried the <base> tag? Create a <base href="/site1/> and place that into the <head>.
That should change any relative urls to use that href as a base. https://www.w3schools.com/tags/tag_base.asp Don't think I've ever used it, but it hopefully will override that behaviour. Cheers, Chris On 19 July 2018 at 09:22, Greg Keogh <[email protected]> wrote: > Folks, I was surprised to find that one storage account == one static > website by creating one special $web container. I was sort of expecting > that containers could be published as distinct websites. So to publish 4 > static web sites I have to create 4 storage accounts, which is a nuisance. > > I thought I could squeeze multiple sites into one $web container by using > pseudo-folders, like this: > > https://foobar.z26.web.core.windows.net/site1 > https://foobar.z26.web.core.windows.net/site2 > --etc-- > > However, if you upload complete static websites into these folders then > the relative links to css files and other pages break. Simple relative > links like href="page2.htm" seem to jump up a level to the root and you get > 404. Same for links to css files. So there's some mixup about where > "relative" links point to from inside a folder. Damn nuisance. > > *Greg K* >
