Forum Discussion

Allwyn_Mascaren's avatar
Oct 17, 2017

HTTP 304 Not Modified in LTM Oracle JDE Deployment



I have a situation where we are loadbalacing to oracle JDE edwards servers.


When accessing the application directly without f5 certain tabs/buttons are visible but while doing so through f5 the application loads in the browser fine but just these tabs/buttons which should be in the center of the page are not loaded.


Everything looks good in the packet capture from f5 - no tcp resets, dups etc. but one server on the backend responds with HTTP 304 NOT MODIFIED. is the BIGIP self ip and the is the backend node.


We are not using web acceleration on the VS so the BIGIP is not caching anything.


Is this HTTP 304 a problem or something else is missing here?


3 Replies

  • Hi allwynmasc,


    Is this HTTP 304 a problem or something else is missing here?


    A Err304 "Not Modified" is not problematic. It happens if the initial Err200 has included a "Last-Modified" HTTP-Header indicating a timestamp value when the content of the requested ressource has beed changed previously.


    For subsequent requests to the same ressource, the client will then include a "If-Modified-Since" HTTP-Header containing the timestamp value of the previously received "Last-Modified" HTTP-Header.


    If the web server noticed that a client sends a "If-Modified-Since" HTTP-Header and the last-change timestamp of the requested ressource is identical, it will respond with a Err304 "Not Modified" response without resending the content again (performance benefit). And if the web server noticed that a client has send an obsolte "If-Modified-Since" timestamp value for the requested ressource, the web server will send a Err200 "OK" alongside with the content of the requested ressource. When the server sends the Err200 "OK" it may again include a new "Last-Modified" timestamp so that the next request to the same ressource could be answered with an Err304 again.


    Note: Instead of using the classic "Last-Modified" HTTP-header, the web server may also send a "Expires" or "Etag" header. So check out for those headers too...


    Cheers, Kai


  • Users can resolve 304 errors by disabling extensions. There is this possibility that there is something wrong with your extensions. Like they could be corrupt, which can be the issue with your browser's ability to receive information. Just disable your extensions to see in case this is the error. In case these things don't work, this issue can be sorted out by executing a more technical process. You might think of asking a web developer or someone in IT to take a look. If you get an HTTP 304, not modified error code, it's because the URL you are looking for has outdated information. To solve it, you'll have to double-check that the error isn't on your side, the client's but instead on the server side.