Ok - this is hard to explain, but, easy to document.
When Interface makes a request for a physics shape as a .obj file it’s also making a strange set of additional requests. Here’s what you see in http server log;
x.x.x.x - - [13/Jan/2016:20:30:40 +0000] "GET /asset/506c13cb798df8967bdb02a0d654983fc14688d4ccfa08a8c0378a4fb3dab36b.obj HTTP/1.1" 304 0 "-" "Mozilla/5.0 (HighFidelityInterface)"
Ok - that’s Interface asking for a compound physics shape with HTTP server returning 304 for not modified as is proper. All good. Then it immediately sends requests for;
x.x.x.x - - [13/Jan/2016:20:30:40 +0000] "HEAD /asset/506c13cb798df8967bdb02a0d654983fc14688d4ccfa08a8c0378a4fb3dab36b.jpg HTTP/1.1" 404 0 "-" "Mozilla/5.0"
x.x.x.x - - [13/Jan/2016:20:30:40 +0000] "HEAD /asset/506c13cb798df8967bdb02a0d654983fc14688d4ccfa08a8c0378a4fb3dab36b.jpeg HTTP/1.1" 404 0 "-" "Mozilla/5.0"
x.x.x.x - - [13/Jan/2016:20:30:40 +0000] "HEAD /asset/506c13cb798df8967bdb02a0d654983fc14688d4ccfa08a8c0378a4fb3dab36b.png HTTP/1.1" 404 0 "-" "Mozilla/5.0"
x.x.x.x - - [13/Jan/2016:20:30:40 +0000] "HEAD /asset/506c13cb798df8967bdb02a0d654983fc14688d4ccfa08a8c0378a4fb3dab36b.tga HTTP/1.1" 404 0 "-" "Mozilla/5.0"
HTTP server responds with 404 - Not found as is proper since there are no such files.
Now - why is Interface doing this? It’s no wonder I notice a much much slower scene populate cycle when I have hundreds of models present with compound shapes. But, even if the overhead would be considered negligible for those superfluous requests - they’re still superfluous. It’s also odd that user agent string changes from .“Mozilla/5.0 (HighFidelityInterface)” to “Mozilla/5.0” and method changes from GET to HEAD.