Hi,
Am 10.06.2020 um 15:34 schrieb Mark Thomas:
> On 10/06/2020 14:07, Paul Carter-Brown wrote:
>> At runtime, any code can call TimeZone.setDefault to change the timezone of
>> the JVM.
>>
>> I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
>> intermittently and seeing
On 10/06/2020 14:07, Paul Carter-Brown wrote:
> At runtime, any code can call TimeZone.setDefault to change the timezone of
> the JVM.
>
> I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
> intermittently and seeing if some code somewhere is changing the timezone.
>
At runtime, any code can call TimeZone.setDefault to change the timezone of
the JVM.
I'd suggest logging TimeZone.getDefault().getDisplayName(Locale.ENGLISH);
intermittently and seeing if some code somewhere is changing the timezone.
Could be in any library...
Paul
On Wed, Jun 10, 2020 at
Hi,
today I've seen something I don't understand: our developers reported an
application that was returning a non-GMT timezone in Date and
Last-Modified headers.
$ curl -v http://localhost:8080
* Rebuilt URL to: http://localhost:8080/
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to
