konveyor / konveyor/rulesets

Create "HTTP cache header" rule(s)

Open
#119 2 comments 0 reactions 0 assignees View on GitHub
kind/feature priority/important-longterm spring-migration/4.2 spring-migration/5 triage/accepted
Dominant language
Java
Stars
6
Forks
49
PR merge metrics
No merged PRs in 30d

Description

According to the [migration guide](https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-4.x#modern-web-interaction-defaults):

> Note that Spring Framework 4.2 comes with revised HTTP cache header processing for resource handling; for common use cases, HTTP caching related headers now have new defaults which do not involve HTTP 1.0 headers such as "Expires" or "Pragma". See [WebContentGenerator.setCacheSeconds](https://docs.spring.io/spring-framework/docs/4.2.0.BUILD-SNAPSHOT/javadoc-api/org/springframework/web/servlet/support/WebContentGenerator.html#setCacheSeconds-int-) and the [new CacheControl class](https://docs.spring.io/spring-framework/docs/4.2.0.BUILD-SNAPSHOT/javadoc-api/org/springframework/http/CacheControl.html) for more details.

Investigate and create rules if necessary for the new header defaults in cache.

In the rule description and message, try to be as verbose and clear as possible. Code examples are always welcome and useful. Feel free to use markdown syntax for these.

Contributor guide

Open the contributing guide

Research direction

Start with the migration guide's HTTP cache header section and inspect WebContentGenerator.setCacheSeconds and the new CacheControl class. Determine which revised defaults need rules, then add clear, verbose rule descriptions and messages with useful Markdown examples; done means the relevant cache-header cases are covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.