#912 new
Mark Piper

Loss of precision in Http.Request.isModified

Reported by Mark Piper | June 14th, 2011 @ 09:54 PM

Consider this test case:

@Test
    public void lossOfPrecisionCausesIsModifiedIssue() throws Exception {
        Http.Request request = newRequest();

        Date now = new Date();
        String etag = "etag";

        String httpFormatDate = Utils.getHttpDateFormatter().format(now);

        request.headers.put("if-modified-since", new Http.Header("if-modified-since", httpFormatDate));
        request.headers.put("if-none-match", new Http.Header("if-none-match", etag));

        //Checking against the same time should mean the request is not modified 
        //this fails
        assertFalse(request.isModified(etag, now.getTime()));

        //this works, because date is normalised first
        assertFalse(request.isModified(etag, Utils.getHttpDateFormatter().parse(Utils.getHttpDateFormatter().format(now)).getTime()));
    }

The problem here is that request.isModified takes a long (i.e. millisecond precision), but that needs to be converted to an HTTP date for the header (second precision). Therefore, converting the HTTP date back into a long will always result in a number that is rounded down from the original. For instance, if now.getTime() = 1308087414635, converting to a HTTP date and then back to a long gives a result of 1308087414000.

Potentially, request.isModified needs to normalise the passed-in long to an HTTP format date first.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by

Pages