The RFC-1123 date-time formatter, such as 'Tue, 3 Jun 2008 11:05:30 GMT'.
!(p)
This returns an immutable formatter capable of formatting and parsing
most of the RFC-1123 format.
RFC-1123 updates RFC-822 changing the year from two digits to four.
This implementation requires a four digit year.
This implementation also does not handle North American or military zone
names, only 'GMT' and offset amounts.
!(p)
The format consists of:
!(ul)
!(li)If the day-of-week is not available to format or parse then jump to day-of-month.
!(li)Three letter {@link ChronoField#DAY_OF_WEEK day-of-week} _in English.
!(li)A comma
!(li)A space
!(li)One or two digits for the {@link ChronoField#DAY_OF_MONTH day-of-month}.
!(li)A space
!(li)Three letter {@link ChronoField#MONTH_OF_YEAR month-of-year} _in English.
!(li)A space
!(li)Four digits for the {@link ChronoField#YEAR year}.
Only years _in the range 0000 to 9999 are supported.
!(li)A space
!(li)Two digits for the {@link ChronoField#HOUR_OF_DAY hour-of-day}.
This is pre-padded by zero to ensure two digits.
!(li)A colon
!(li)Two digits for the {@link ChronoField#MINUTE_OF_HOUR minute-of-hour}.
This is pre-padded by zero to ensure two digits.
!(li)If the second-of-minute is not available then jump to the next space.
!(li)A colon
!(li)Two digits for the {@link ChronoField#SECOND_OF_MINUTE second-of-minute}.
This is pre-padded by zero to ensure two digits.
!(li)A space
!(li)The {@link ZoneOffset#getId() offset ID} without colons or seconds.
An offset of zero uses "GMT". North American zone names and military zone names are not handled.
</ul>
!(p)
Parsing is case insensitive.
!(p)
The returned formatter has a chronology of ISO set to ensure dates _in
other calendar systems are correctly converted.
It has no override zone and uses the {@link ResolverStyle#SMART SMART} resolver style.
The RFC-1123 date-time formatter, such as 'Tue, 3 Jun 2008 11:05:30 GMT'. !(p) This returns an immutable formatter capable of formatting and parsing most of the RFC-1123 format. RFC-1123 updates RFC-822 changing the year from two digits to four. This implementation requires a four digit year. This implementation also does not handle North American or military zone names, only 'GMT' and offset amounts. !(p) The format consists of: !(ul) !(li)If the day-of-week is not available to format or parse then jump to day-of-month. !(li)Three letter {@link ChronoField#DAY_OF_WEEK day-of-week} _in English. !(li)A comma !(li)A space !(li)One or two digits for the {@link ChronoField#DAY_OF_MONTH day-of-month}. !(li)A space !(li)Three letter {@link ChronoField#MONTH_OF_YEAR month-of-year} _in English. !(li)A space !(li)Four digits for the {@link ChronoField#YEAR year}. Only years _in the range 0000 to 9999 are supported. !(li)A space !(li)Two digits for the {@link ChronoField#HOUR_OF_DAY hour-of-day}. This is pre-padded by zero to ensure two digits. !(li)A colon !(li)Two digits for the {@link ChronoField#MINUTE_OF_HOUR minute-of-hour}. This is pre-padded by zero to ensure two digits. !(li)If the second-of-minute is not available then jump to the next space. !(li)A colon !(li)Two digits for the {@link ChronoField#SECOND_OF_MINUTE second-of-minute}. This is pre-padded by zero to ensure two digits. !(li)A space !(li)The {@link ZoneOffset#getId() offset ID} without colons or seconds. An offset of zero uses "GMT". North American zone names and military zone names are not handled. </ul> !(p) Parsing is case insensitive. !(p) The returned formatter has a chronology of ISO set to ensure dates _in other calendar systems are correctly converted. It has no override zone and uses the {@link ResolverStyle#SMART SMART} resolver style.