Three.js Loading .OBJ error in Azure but not Locally

Question

I am using three.js for webGL to load .obj but I have a problem when loading .obj in Windows Azure runnning Windows Server 2008 I using Google chrome browser and it gives th

Answer 1

[SOLVED] LOADING .OBJ (Wavefront) FILE IN WINDOWS HOSTING RETURN 404 ERROR [SOLVED]

As I was Working with Three.js and loading a .obj file works great for me in localhost but when running the files from the Windows Hosting it return 404 for the .obj file.

So, we need to add this lines to the web.config file of the project root folder (if you don't have the file in your project root folder then go ahead and create one. )

web.config

        <?xml version="1.0" encoding="UTF-8"?>
        <configuration>
            <system.webServer>
                 <staticContent>
                        <mimeMap fileExtension=".obj" mimeType="application/octet-stream" />
                 </staticContent>
            </system.webServer>
        </configuration>

Place the web.config to correct location and Enjoy :)

Answer 2

I found an answer to my problem, is because the file extension .obj is not yet map to the MIME type in my Azure server:

Check the link below on how to add it:

http://technet.microsoft.com/en-us/library/cc725608(v=ws.10).aspx

and you could check here for the MIME type:

http://filext.com/file-extension/OBJ

Once you have map .obj to MIME, you will have no problem to load it anymore! :)

Answer 3

I thought I should add what I ended up doing after finding this post. I'm using .mtl files for material (in addition to the .obj) for a THREE JS project. Since I'm using MTLLoader to get the materials as well (my models aren't just flat-color), I had to add the following line:

web.config

 <!-- Instruct IISNODE to treate .obj+.mtl models as application/octet data -->
<configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension=".obj" mimeType="application/octet-stream" />
            <mimeMap fileExtension=".mtl" mimeType="application/octet-stream" />
        </staticContent>
    </system.webServer>
</configuration>

Answer 4

You will need to add a mime type definition in your application to tell IIS how this file should be served. The mime map referred to in the error message should be defined in the web.config file. Here's an example.

<system.webServer>
     <staticContent>
            <mimeMap fileExtension=".mp4" mimeType="video/mp4" />
            <mimeMap fileExtension=".m4v" mimeType="video/m4v" />
     </staticContent>
 </system.webServer>

Click on the link below for a full list of mime types:

Full list of mime types.