fix: Added Locale.ENGLISH to SimpleDateFormat for parsing the Last-Modified HTTP header

[kuaikuai]

Added Locale.ENGLISH to SimpleDateFormat for parsing the Last-Modified HTTP header. This makes the date parsing locale - specific to English, avoiding possible parsing issues caused by default locale differences.

[gemini-code-assist[bot]]

Summary of Changes

Hello @kuaikuai, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the reliability of date parsing within the GoFeatureFlagApi by explicitly setting the locale to English when interpreting the Last-Modified HTTP header. This ensures that date strings, which are standardized to an English format in HTTP, are correctly parsed regardless of the JVM's default locale, thereby preventing unexpected parsing failures and improving the stability of the API's interaction with HTTP responses.

Highlights

• Locale Specification for Date Parsing: Explicitly added Locale.ENGLISH to the SimpleDateFormat constructor used for parsing the Last-Modified HTTP header.
• Improved Robustness: This change prevents potential ParseException errors that could arise from variations in the default system locale when interpreting date strings from HTTP headers, ensuring consistent parsing behavior.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

[thomaspoignant]

@kuaikuai thanks for this PR, there is a formatter issue that blocks the CI could you have a look?

Also I've seen the gemini review and this implementation is probably better to what I've written. If you have some time and willing to contribute to the provider by changing that it would be awesome.

If you can't this is not a problem, you can just fix the formatting part, and we can release a new version of the provider, and I will work on updating the way to read the headers later.

[thomaspoignant]

/gemini review

[kuaikuai]

@kuaikuai thanks for this PR, there is a formatter issue that blocks the CI could you have a look?

Also I've seen the gemini review and this implementation is probably better to what I've written. If you have some time and willing to contribute to the provider by changing that it would be awesome.

If you can't this is not a problem, you can just fix the formatting part, and we can release a new version of the provider, and I will work on updating the way to read the headers later.

I submitted the code directly through the GitHub web interface, so it’s not easy to ensure proper formatting. I’ll make some adjustments to fix this. ^_^

[kuaikuai]

` The DateTimeFormatter.RFC_1123_DATE_TIME in Java does not use ResolverStyle.STRICT by default.

If strict parsing is required , simply using DateTimeFormatter.RFC_1123_DATE_TIME as-is may not be sufficient.

This means it may accept some lenient or ambiguous inputs that strictly conforming RFC 1123 date-time strings should reject. Unfortunately, you cannot directly modify the resolver style of the predefined RFC_1123_DATE_TIME formatter, so achieving strict parsing requires additional work — such as creating a custom formatter based on it with ResolverStyle.STRICT. It is more complex than SimpleDateFormat("EEE, dd MMM yyyy HH:mm:ss zzz", Locale.ENGLISH).

SimpleDateFormat can be sufficient for specific use cases — especially when dealing with HTTP headers (like Last-Modified) where the format is well-known and consistently formatted per RFC 1123. `