Pull request #1334 introduced a new screen during the Hold state that only allows you to Resume or Stop the current job.
This PR reverts back to the previous behavior which will allowed it to serve up file requests when inMotionState() is false, even in Hold state.
This is in agreement to the screen that shows when in motion, that appears to say that issuing a feedhold is recommended to be able to reload the WebUI.
304 responses
This PR also adds a check when in motion that will return a 304 when the correct ETag is received and the hash of the file is already cached in memory.
This should reduce the amount of times that the cut down UI is seen if the file needs to be retrieved again for some reason.
Hold State Requests
Pull request #1334 introduced a new screen during the Hold state that only allows you to Resume or Stop the current job.
This PR reverts back to the previous behavior which will allowed it to serve up file requests when
inMotionState()is false, even in Hold state.This is in agreement to the screen that shows when in motion, that appears to say that issuing a feedhold is recommended to be able to reload the WebUI.
304 responses
This PR also adds a check when in motion that will return a 304 when the correct ETag is received and the hash of the file is already cached in memory.
This should reduce the amount of times that the cut down UI is seen if the file needs to be retrieved again for some reason.