You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Init sample object on a page running on an iPad's Safari with iOS 8.0 or
8.1.1
2. Then reinit object without refreshing the page
3. It was tested on Apache 2.2.+
What is the expected output? What do you see instead?
After reinit 3d objects can't be loaded properly.
What version of the product are you using? On what operating system?
Safari, iPad, iOS 8.0 or 8.1.1, Apache 2.2.+
Please provide any additional information below.
jsc3d uses XMLHTTPRequest's POST method for loading static files. After second
use of the same 3d model without refreshing a page, browser tries to use a
cached version of the file and receives 412 status from the server so the
library can't load the files properly. According to RFC 2616 which is a
specification for HTTP/1.1 protocol http://www.ietf.org/rfc/rfc2616.txt
receving 412 status seems to be ok when http client tries to use a cache of the
content with the POST method and it is a counterpart of 304 Not Modified status
for GET method. In my opinion the library should also handle 412 status by
trying to load a file in the next attempt by using GET method or every time
while loading obj/mtl files with POST should add some random variable (e.g.
timestamp) to their urls. It can also use GET instead of POST.
Of course the problem could be fixed by not attaching the HTTP's ETag header
(which is used for caching) by the server sending obj/mtl files or by not
initializing the same 3d objects more than once without refreshing the page.
But I use a 3rd-party software which uses jsc3d library in that manner so it is
not the case to fix this there.
Original issue reported on code.google.com by [email protected] on 26 Nov 2014 at 12:13
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 26 Nov 2014 at 12:13The text was updated successfully, but these errors were encountered: