From: akr@...
Date: 2015-06-14T14:34:08+00:00
Subject: [ruby-core:69584] [Ruby trunk - Bug #11261] Time.parse of javascript formatted timestamp: wrong results in certain timezones

Issue #11261 has been updated by Akira Tanaka.


It seems that Date._parse recognizes NOV as November.

```
% ruby -rdate -e 'p Date._parse("Mon May 18 2015 22:16:38 GMT+0600 (NOVT)")[:mon]'
11
% ruby -rdate -e 'p Date._parse("Mon May 18 2015 22:16:38 GMT+0600")[:mon]'       
5
% ruby -v                                                                  
ruby 2.3.0dev (2015-01-02 trunk 49103) [x86_64-linux]
```



----------------------------------------
Bug #11261: Time.parse of javascript formatted timestamp: wrong results in certain timezones
https://bugs.ruby-lang.org/issues/11261#change-52922

* Author: Andrey Novikov
* Status: Open
* Priority: Low
* Assignee: 
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
If I try to parse a string generated by javascript's `new Date()`  (seems like RFC 2822 with timezone name specified) in a browser located in `Asia/Novosibirsk` timezone I will get 1st of November quite frequently.

    require 'time'
    Time.parse('Mon May 18 2015 22:16:38 GMT+0600 (NOVT)')
    # => 2015-11-01 22:16:38 +0600



-- 
https://bugs.ruby-lang.org/