I've finally figured out why JQM and other clients that use the premise web server (known internally within Premise as the WebClient) have such horrible behavior when they try to access files/resources that don't exist.
For example, notice how if a .gif or .png on the server is missing the web browser spins in a 'loading state' forever?
This is because, in the case of static file requests, WebClient simply does nothing if it can't find the resource. It is supposed to return an HTTP 404 status in these cases. It doesn't even close the socket.
This is why navigating in a web browser to, say http://home:86/foo where /foo doesn't exist just spins the browser until the connection times out.
Blarg.
For example, notice how if a .gif or .png on the server is missing the web browser spins in a 'loading state' forever?
This is because, in the case of static file requests, WebClient simply does nothing if it can't find the resource. It is supposed to return an HTTP 404 status in these cases. It doesn't even close the socket.
This is why navigating in a web browser to, say http://home:86/foo where /foo doesn't exist just spins the browser until the connection times out.
Blarg.
