Skip to content
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

Modified-time often gets useless values and is of questionable value #12379

Closed
dsoprea opened this issue Mar 6, 2017 · 1 comment
Closed

Modified-time often gets useless values and is of questionable value #12379

dsoprea opened this issue Mar 6, 2017 · 1 comment

Comments

@dsoprea
Copy link

@dsoprea dsoprea commented Mar 6, 2017

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.03.06. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

  • I've verified and I assure that I'm running youtube-dl 2017.03.06

Before submitting an issue make sure you have:

  • At least skimmed through README and most notably FAQ and BUGS sections
  • Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

  • Bug report (encountered problems with youtube-dl)
  • Site support request (request for adding support for a new site)
  • Feature request (request for a new functionality)
  • Question
  • Other

This issue indicates that the modified-time is set based on the "Last-Modified" header: #9386

I'm not sure that setting the modified-time produces much value. I downloaded one video and the mtime is exactly one year earlier than the date on the YouTube page. I downloaded another and the mtime is set to now. If the timestamp isn't intuitive, predictable, or what people otherwise expect it to be, then it seems useless and confusing.

I'm +1 for killing it. It seems like most people would prefer passing the switch to disable it if they knew how truly unpredictable it could be. Thoughts?

@yan12125
Copy link
Collaborator

@yan12125 yan12125 commented Mar 6, 2017

There was a discussion for the same issue: #1709. Please move there for further discussions, thanks!

@yan12125 yan12125 closed this Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.