spring-cloud / spring-cloud/spring-cloud-gateway

LocalResponseCache support for Spring Cloud Gateway Server Web MVC

Open
#4,182 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
4.9k
Forks
3.5k
Avg merge
20h 57m
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
We would like to be able to cache responses and would therefore appreciate a filter in the Web MVC stack similar to the existing LocalResponseCache GatewayFilter in the Webflux stack.

Although we found the following page in the current documentation, we can't find a way to configure this filter or the code outlined in the documentation.

Describe the solution you'd like
The ability to configure a ResponseCache in the Web MVC stack in the same way as in the Webflux stack.

Describe alternatives you've considered
Implementing the filter ourselves. But this presents us with some challenges.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the existing LocalResponseCache GatewayFilter in the WebFlux stack with the documented Local Cache Response Filter for Server Web MVC. Check how the Web MVC filter is configured and where the documentation's code fits in the project. Done means a ResponseCache can be configured in Web MVC in the same way as in WebFlux, with the documentation matching the available implementation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.