Closed jayryemure closed 5 years ago
Interesting, I hadn't tried using a full domain in the publicPath
before. Is there any reason you're configuring it that way instead of just using /
?
I just added a unit test for this case, and it is failing even on Mac. I'll look and see if I can fix it and get back to you.
Thanks for bringing this to my attention! I've fixed the bug and released the fix in version 1.0.13
.
Please confirm if it's now fixed for you and we can close this issue.
@jharris4 I've confirmed that it works for me on 1.0.13
, thanks for the fix.
One of the forward slashes in the URL protocol seems to be removed from the outputted public path.
http://[foo]
tohttp:/[foo]
Ex:
Actual Result:
<link href="https:/www.foo.com/content/css/main.min.2976747713ab1fa371cde6441e3cfdef.css" rel="stylesheet"></head>
(https:/)
Expected Result:
<link href="https://www.foo.com/content/css/main.min.2976747713ab1fa371cde6441e3cfdef.css" rel="stylesheet"></head>
(https://)
Env: