spring-boot-http-client

A set of rules for making outbound HTTP calls in Spring Boot applications. It covers naming, configuration, timeouts, credentials, and the choice between RestClient and WebClient.

In plain words
What is it for?
Use it when building or reviewing Spring Boot HTTP clients, adapters, configuration classes, properties, and integrations with remote APIs.
Why use it?
It makes external service calls consistent and predictable while keeping credentials and endpoint addresses outside the code. Explicit timeouts and bounded resilience reduce the risk of calls hanging indefinitely.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/lsampaioweb/ai-instructions/spring-boot-http-client
Clone the repo
git clone --depth 1 https://github.com/lsampaioweb/ai-instructions

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00518
Opus 5 $0.00000 $0.00259
Sonnet 5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash 7ef23d70aef4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spring-boot-http-client scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/spring-boot-http-client.mdc · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spring Boot HTTP Client

Naming Conventions

  • Suffix HTTP client classes with HttpClient.
  • Suffix HTTP adapter classes with HttpAdapter.
  • Suffix HTTP configuration properties classes with HttpProperties.
  • Name HTTP client @Configuration classes with the *HttpConfiguration suffix (e.g., UserHttpConfiguration, PaymentHttpConfiguration).

Rules

  • Keep outbound client configuration centralized in a dedicated configuration class.
  • Use RestClient (Spring Framework 6.1+) as the default for imperative HTTP calls.
  • Use WebClient only when reactive streams are required.
  • Keep endpoint URLs and credentials externalized in properties.
  • Bind HTTP client properties using @ConfigurationProperties annotated with @Validated.
  • Keep external-call initialization explicit and deterministic.
  • Inject RestClient.Builder into the service class and construct the RestClient instance in a @PostConstruct method using the bound properties.
  • Keep outbound connection and read timeout values explicit and externally configurable.
  • Use connectionTimeout=5s and readTimeout=30s as default timeout values unless the remote API's SLA explicitly requires different values.
  • Keep error handling explicit for non-success HTTP responses.
  • Register .onStatus() handlers on every RestClient call chain to map HTTP error responses to domain exceptions before they propagate to the service caller.
  • Keep status-specific failure mapping explicit when remote APIs expose known error classes.
  • Apply retry logic only for idempotent HTTP methods (GET, PUT, DELETE, HEAD), or for POST/PATCH when the remote API explicitly confirms idempotency.
  • Keep generic response mapping type-safe.
  • Use ParameterizedTypeReference for all generic response types (e.g., List<T>, PagedModel<EntityModel<T>>) to preserve type information at deserialization.
  • Keep outbound request construction isolated from the controller layer.
  • Use UriComponentsBuilder for all dynamic URL construction in outbound calls.

Read the full file on GitHub · 37 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 37 lines · 0 tokens per session scan A 7ef23d70aef4

Subscribe to this mod's changes

spring-boot-http-client is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.