go to bug id or search bugs for
The date constant format is different.
Reference material for RFC1123.
php -r "echo gmdate(DATE_RFC1123, gmmktime(0,0,0,1,1,2018));"
Mon, 01 Jan 2018 00:00:00 GMT
Mon, 01 Jan 2018 00:00:00 +0000
Add a Patch
Add a Pull Request
You know we aren't Microsoft, right?
The actual RFC 1123 says
> There is a strong trend towards the use of numeric timezone
> indicators, and implementations SHOULD use numeric timezones
> instead of timezone names.
And the standard there is basically just a slight adjustment to RFC 822's which describes the timezone as
> zone = ... / ( ("+" / "-") 4DIGIT ) ; Local differential hours+min. (HHMM)
And the actual output from PHP matches what the documentation describes. So I don't know what bug you're reporting.
If anything it's .NET that's difficult because the format string clearly outputs "GMT" as the timezone, which is alluded to in the general date/time formatting docs:
> Although the RFC 1123 standard expresses a time as Coordinated Universal Time (UTC), the formatting operation
> does not modify the value of the DateTime object that is being formatted. Therefore, you must convert the
> DateTime value to UTC by calling the DateTime.ToUniversalTime method before you perform the formatting
The most common return value was an RFC-1123 formatted date stamp
alert('RFC-1123 formatted date stamp is ' + (new Date).toUTCString())
Use your words. Full sentences.
If you aren't comfortable writing English then use your native language. Either way, speak, don't link.
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.