WebGL Build looking in the wrong place

As mentioned in a previous post, I have never got the WebGL builds working, and I absolutely hate working with WebGL in general.

Now that we have the formalities out of the way, a little background.

Since Unity 5 was released, I have worked on and off to get these afwul builds to run, with absolutely no success.

My latest attempt has pointed me to the possibility that the builds are pointing themselves to the wrong place entirely.

On one of my development domains here: http://briggsmotors.co.uk/3dartwork/portfolio/1shinytiles/index.html
I have a simple model viewer to test a substance, but the js files referenced, point to the wrong places in the Compressed folder.
http://briggsmotors.co.uk/3dartwork/portfolio/1shinytiles/Release/1ShinyTiles.js
http://briggsmotors.co.uk/3dartwork/portfolio/1shinytiles/Release/fileloader.js
http://briggsmotors.co.uk/3dartwork/portfolio/1shinytiles/Release/UnityConfig.js

If you look at the “Requested URL” section of each of these pages, you see that an extra “/” has been added to the end of the URL between the file name and file extension, I think this is what is causing the problem.

I have looked inside these files and am at a complete loss as to work out what they actually are, and there are no links to these in there at all.

I have not modified them, Unity generates them this way, any suggestions to even getting these working? then I can work on the distinct graphics differences.

I don’t see an extra slash anywhere in the URLs for those JS files. They simply are not located at …/1shinytiles/* (thus the 404 responses).

Can you verify that the Release folder is located in that 1shinytiles folder on the server? If it is, then the request is getting routed incorrectly which could mean that it is trying to redirect the /Release* request to the /Compressed folder and perhaps the /Compressed folder is missing.

I have just checked the server via FTP, and can confirm that both these folders exist and have valid files, the build works if run locally in Firefox, but all other browsers say it needs to be run on a server.

I do agree that it is possible the redirected request is being lost somewhere, especially considering that I have built 3 different builds from different projects and tried them on different domains and hosting packages (Windows and Linux).

I made a screenshot of my FTP file system here:
2307244--155425--Temp.png

Oh sorry, you’re right. The requested URL/physical path in the error report does show the extra slash. That means whatever is changing your request to the Compressed folder (i.e, a redirect handler in IIS/web.config) is changing the final path incorrectly.

Do you know what method your application is using to rewrite the original URL request?

No, unfortunately I don’t.
There was a previous site but at this domain location, but all that has been removed.
Whatever the server is using, it is down to my host, not me, but I have never had this problem before and I have developed several sites using this host.

As I stated earlier, I have not edited any of this, so what Unity created, is what is up there.

I just don’t know what could be causing the extra slash.

I’m afraid youll have to talk to your host or if you can modify your web.config directly, it can be done through that.

We used the method laid out in this post: SOLVED: IIS - configuring it to serve out the new WebGL stack files - how? - Unity Engine - Unity Discussions

But have since moved the JS content to a CDN and simply configured that to our needs.