HSTSWRITEFUNCTION stops being called as soon as an stsentry with expires set to TIME_T_MAX is found due to
I did this
(sorry, right now I cannot provide a source code to easily reproduce this - I hope just this description is enough)
Created an easy handle and set the option
Assume that if there is no
And if there is no
I have also set the
Finally, I made a request against
I expected the following
The cache saved has 3 items where only the second one was updated (with the new expire retrieved from the host after the request). However, what happens is that
I did some debugging, and it seems that when the easy handle is closed and
This causes the call to
I can default it to a value that is still far in the future, but not big enough to cause the overflow error. However this should probably be handled differently in case it is a real bug. If it is not, feel free to close this.
The text was updated successfully, but these errors were encountered:
When setting a blank expire string, meaning unlimited, curl would pass TIME_T_MAX to getime_r() when creating the output, while on 64 bit systems such a large value cannot be convetered to a tm struct making curl to exit the loop with an error instead. Starting now, unlimited expiry is instead handled differently by using a human readable expiry date spelled out as "unlimited" instead of trying to use a distant actual date. Test 1660 and 1915 have been updated to help verify this change. Reported-by: Jonathan Cardoso Fixes #7720
@bagder not really related to this issue, but I just noticed that if
I was expecting the request to be aborted with
Important to notice that I'm using the multi interface.
It sounds like a separate issue. And I think we should clarify in the docs what it means to return an error there. I think it should fail the transfer...