New issue
Advanced search Search tips

Issue 696184 link

Starred by 2 users
Status: Duplicate
Merged: issue 693053
Owner: ----
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

document.lastModified returns bogus date when Last-Modified HTTP header is malformed

Reported by mishra.d...@gmail.com, Feb 25 2017 
UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0

Steps to reproduce the problem:
Upstream Bug :  693053 

I am able to reproduce this issue in Chrome Beta Linux.

What is the expected behavior?
Current date is displayed.

What went wrong?
(1) Run the attached python script. It will start a local http server on port 9999.
(2) Open the URL "http://localhost:9999/"

Result :
"01/00/0000 00:00:00" is displayed.

Did this work before? N/A 

Chrome version: 57.0.2987.54 (Official Build) beta (64-bit)  Channel: beta
OS Version: V8 5.7.492.44
Flash Version: Shockwave Flash 24.0 r0
invalid_last_modified.py
677 bytes View Download

Comment 1 by elawrence@chromium.org, Feb 26 2017

Components: Blink>DOM
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
This isn't a security vulnerability; it's not clear that this behavior is functionally correct though; it looks like the default should be the current datetime.

Code: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/Document.cpp?l=4753

Comment 2 by elawrence@chromium.org, Feb 26 2017

Mergedinto: 693053
Status: Duplicate (was: Unconfirmed)
The reason that I couldn't see how the code does this is that it doesn't. Because someone else reported this bug a while ago and it was fixed.

Please do not refile duplicate bugs.
►

Sign in to add a comment