You are viewing a plain text version of this content. The canonical link for it is here.
Posted to olio-dev@incubator.apache.org by "Shanti Subramanyam (JIRA)" <ji...@apache.org> on 2009/06/12 18:24:07 UTC

[jira] Resolved: (OLIO-90) Simulation of browser caches incorrect

     [ https://issues.apache.org/jira/browse/OLIO-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shanti Subramanyam resolved OLIO-90.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2

This issue was fixed by retrieving statics with a if-modified-since header when simulating browser caching behavior. For non-cached sessions, we still retrieve the statics only once per session. In this case, we assume that the application has set an expiry on the page that is well into the future. This is also true for the retrieval of all image files - we assume that these can be cached as long as the user session is valid. 

On testing after the fix, there is a slight (0.5%) increase in network utilization at 500 users. So a large scale test is bound to show a more substantial increase in network traffic - these are all small packets as no real data is getting sent.

> Simulation of browser caches incorrect
> --------------------------------------
>
>                 Key: OLIO-90
>                 URL: https://issues.apache.org/jira/browse/OLIO-90
>             Project: Olio
>          Issue Type: Bug
>          Components: generic
>    Affects Versions: 0.1
>            Reporter: Shanti Subramanyam
>            Assignee: Shanti Subramanyam
>            Priority: Minor
>             Fix For: 0.2
>
>
> The driver simulates browser caches by not requesting the images included in a page 40% of the time. In reality, browsers make an 'if-modified-since' request to the server and the server checks if the file was modified later than the date specified in the request and if so it will return the file. Thus, this will incur an additional request/response cycle which we are not capturing in the driver/server interaction.
> This bug will require fixes to both the driver and the server side. The driver can use a timestamp equivalent to when the run started. The server code (for PHP) must check for the existence of the if-modified-since flag. For rails, since the app does not service these files, the server will automatically take care of the request.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.