-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ParseException when publishing batch to SNS #1293
Comments
Thanks for the bug report, @schurmann. I cannot reproduce the error on my end—all the responses I see from SNS include a |
It occurs very rarely for me, so I suspect it will be difficult to reproduce. I'm connecting to eu-central-1 and haven't tried any other regions. When the FYI: I see that the java sdk swallows any parsing exceptions, so there is a difference in behavior. Not sure if that is intended or not. |
I still cannot reproduce the bad date responses, even in eu-central-1. If I could then I'd be able to communicate the bad values to the SNS team and hopefully resolve the problem at the source. That said, the |
|
The problem still exists with Smithy 1.3.3 :(
|
Describe the bug
When publishing a batch to SNS, I sometimes see ParseException. This happens when
ClockSkewInterceptor
is parsing theDate
response header to detect clock skew andDate
header is using an obsolete format with 2 digits year. When the format is 4 digit year, it works correctly,Expected behavior
The
Date
response header should parse the obsolete format correctly.Current behavior
Steps to Reproduce
Possible Solution
Use correct format for the
Date
header in the SNS response or allow year to be 2 digits.Context
No response
AWS Kotlin SDK version used
1.0.31
Platform (JVM/JS/Native)
JVM
Operating System and version
N/A
The text was updated successfully, but these errors were encountered: