New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assets controller not handling IE If-Modified-Since #3569
Comments
It's annoying when browsers don't follow the spec, but I guess it's better to be lenient, especially with commonly-used browsers. |
Seems like @gmethvin fixed it already in master. |
Oops. I was going to submit a separate PR for that and somehow it got included in #3478. That should work but I was meaning to add some tests as well. I'm happy to revert/change as necessary. |
Goes to show how carefully I review things submitted by @gmethvin. I wonder what other changes you've piggy backed onto PRs that I've merged? 😃 |
I seem to be having a similar problem as the IE complaint, but I'm not sure the source exactly. However, it is very similar:
|
It appears this occurs when I am accessing endpoints themselves defined in my Play application:
|
In case it's helpful, I upped versions of play and joda-time, which gave same exception but deeper stack:
|
And one more note, I'm using client Chrome, Version 39.0.2171.95 m. |
Use a regex to recognize the date format and discard any extra trailing information. Then use one of two date formats to do the parsing. See playframework#3569.
Fixed in #3792. |
Use a regex to recognize the date format and discard any extra trailing information. Then use one of two date formats to do the parsing. See playframework#3569.
2.3.6: IE (at least 9 through 11, and apparently old firefox, too) sends weird
If-Modified-Since
headers that can include an extra length value:Not a huge issue, but it seems safe enough to ignore the extra stuff. (Also, "invalidate"?)
The text was updated successfully, but these errors were encountered: