jetty/jetty.project

Jetty 12: Implement HttpClient cache

Open

#11076 opened on Dec 15, 2023

View on GitHub
 (15 comments) (0 reactions) (1 assignee)Java (3,701 stars) (1,913 forks)batch import
EnhancementHelp Wanted

Description

Jetty Version 12.0.1

Jetty Environment Client API

Java Version 21.0.1

Question It's not clear to me how Jetty Client can respect Cache-Control headers without having a client-side cache to pull cached responses out of. But on the other hand, I can't find any sort of mention of a client-side cache in the documentation.

Can you please clarify what the client supports or does not support with respect to client-side caching?

Contributor guide

Tech stack
java
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Java programmingHTTP protocol knowledgeCaching concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Review the Jetty HttpClient implementation in the jetty client module, specifically the HttpExchange and caching related classes. Look at the comments in the issue for any guidance from maintainers about desired behavior. Consider existing HTTP cache implementations in other Java HTTP clients for reference. The issue appears to be a feature request, so research should focus on designing a client side cache that respects Cache Control headers.