Thanks for the response!
Well, I don't really know if it conforms to the standard or not, but
this "GMT" string is used by web servers (at least some of them). It's
parsed with no issues using JavaScript.
We use QDateTime::toString to parse HTTP responses. Our users are
complaining it's not working anymore, that's why I had to create this
report..
On 6/19/2023 2:27 PM, Axel Spoerl via Interest wrote:
Hi Alexander,
the reason for the assertion is the "GMT" string. RFC2822 expects the
time zone to be specified as an offset from UTC (e.g. "-0200"). If no
offset is specified, the timezone is assumed to be UTC.
UTC (or GMT) as an explicit specification as a string would not make
much sense and is therefore not tolerated.
That's the format, QDateTime::fromString() accepts.
Not sure, if and why UTC/GMT was accepted prior Qt 6, if that's a bug
or even a regression. I'll check this and respond to the Jira ticket.
Cheers
Axel
------------------------------------------------------------------------
*Von:* Interest <interest-boun...@qt-project.org> im Auftrag von
Alexander Dyagilev <alervd...@gmail.com>
*Gesendet:* Montag, 19. Juni 2023 12:51
*An:* Qt Interest <interest@qt-project.org>
*Betreff:* [Interest] QDateTime::fromString does not work with
Qt::RFC2822Date
Hi guys,
Am I an idiot, or is it really QDateTime::fromString which is broken
since at least Qt 6.2.4 ?
I've created the bug report here:
https://bugreports.qt.io/browse/QTBUG-114681
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
