[
https://issues.apache.org/jira/browse/AXIS2C-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1527.
-------------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
The axutil_date_time_local_to_utc function was reading year and month
values that were already in tm format (years since 1900, 0-indexed months)
but treating them as actual calendar values. Then at the end, it converted
them to tm format again, causing double-conversion.
For example, input "2010-01-01T00:00:00+02:00" would:
- Be stored as year=110, mon=0 (tm format)
- Read as year=110, mon=0 (treated as actual values)
- Output year=110-1900=-1790 (garbage)
The fix converts from tm format to actual values at the start of the
function, so calculations use real year/month values. The existing
conversion at the end correctly converts back to tm format.
> Local to UTC time calculation wrong.
> ------------------------------------
>
> Key: AXIS2C-1527
> URL: https://issues.apache.org/jira/browse/AXIS2C-1527
> Project: Axis2-C
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: Linux CentOS running server. Windows XP Pro running
> client (web browser: Firefox).
> Reporter: Daniel Gorodowienko
> Priority: Minor
> Fix For: 2.0.0
>
>
> When using axutil_date_time_local_to_utc with '2010-01-01T00:00:00+02:00',
> '110-11-30T22:00:00.000Z' returned.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
