Open musicist288 opened 11 years ago
These are good thoughts - do you want to contribute?
A workaround right now would be mesh.file = http://site.com/projects/114/meshes/8/?.stl
just pass something to the url so that the parser grabs the extension but the webserver is not confused.
Thanks. I can use that work around for the time being. I've forked the repo and will look into implementing this flexibility.
Consider the following:
Note
mesh.file
is a RESTful identifier. Currently this code crashesthis.meshRenderer
because it seems that the parser cannot decide what kind of file it is, or is using a default parsing scheme that is incorrect. However in the response headers there are the following headers:I think it would be a good idea to detect headers of this sort to not have to force the user into including the name of the file in the url. Preferably the Content-Type would be the dominant indicator and a fallback to the Content-Disposition filename.