You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually the warnings are generated only when the application runs in a container not on Ubuntu 18.04.
The container is generated trough a Maven build of a Spring Boot based application that uses Cloud Native BuildPacks (docs here). I don't know exactly which distro is running in the generated container.
I feel this is not really a bug, but a feature request to expose the CookieSpec configuration in the SDK Apache HttpClient.
I'll research more about it, maybe there's a way to configure through an environment variable as a workaround?
Reacted by Alessandro Falappa and Michael Nico Suarez
Yeah I couldn't find a way either. We've added this to our backlog, not necessarily a direct access to the CookieSpec config, but a way to fix the warnings you're seeing in the HttpClient.
Reacted by Alessandro Falappa, nucl3ar_bean and Bill Orpet
Thanks for submitting the issue. As of v2.46.0, the SDK's default sync HTTP client is Apache5HttpClient (Apache HttpClient 5.x), which defaults to RFC 6265 cookie handling. The legacy RFC 2109/2965 cookie parsers that produced the Invalid 'expires' attribute warning don't exist in Apache 5, so this warning no longer occurs on the default path.
If you're explicitly using ApacheHttpClient (Apache 4.x), migrating to Apache5HttpClient should resolve this.
Hence, closing this as "not planned", thanks for the report.
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Activity
AlexFalappa commentedon Apr 19, 2021
Actually the warnings are generated only when the application runs in a container not on Ubuntu 18.04.
The container is generated trough a Maven build of a Spring Boot based application that uses Cloud Native BuildPacks (docs here). I don't know exactly which distro is running in the generated container.
debora-ito commentedon Apr 21, 2021
I feel this is not really a bug, but a feature request to expose the CookieSpec configuration in the SDK Apache HttpClient.
I'll research more about it, maybe there's a way to configure through an environment variable as a workaround?
AlexFalappa commentedon Apr 21, 2021
I have found no way to configure the
CookieSpecvia environment variable or system propertiesdebora-ito commentedon Apr 24, 2021
Yeah I couldn't find a way either. We've added this to our backlog, not necessarily a direct access to the
CookieSpecconfig, but a way to fix the warnings you're seeing in the HttpClient.Andrew-Sheridan commentedon Nov 8, 2021
I am receiving essentially the same warnings while using spark to write to s3.
using
pyspark 3.1.1"spark.jars.packages": "com.amazonaws:aws-java-sdk-s3:1.12.105,org.apache.hadoop:hadoop-aws:3.1.1",add STANDARD cookie spec
hummerstudio commentedon Mar 21, 2023
Apache 5.1.3 is compliant with RFC 6265 by default. It works!!
bhoradc commentedon Aug 25, 2026
Hi @AlexFalappa
Thanks for submitting the issue. As of
v2.46.0, the SDK's default sync HTTP client isApache5HttpClient(Apache HttpClient 5.x), which defaults toRFC 6265cookie handling. The legacyRFC 2109/2965cookie parsers that produced theInvalid 'expires' attributewarning don't exist in Apache 5, so this warning no longer occurs on the default path.If you're explicitly using
ApacheHttpClient(Apache 4.x), migrating toApache5HttpClientshould resolve this.Hence, closing this as "not planned", thanks for the report.
github-actions commentedon Aug 25, 2026
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.