swagger-api / swagger-api/swagger-codegen

Do not use the tool any more. Had to change all usage of RestTemplate to use HttpClient directly or even use read/write to a socket. RestTemplate it uses is no good. Cannot pass any custom header, keep getting 400 bad request, that's all with client generated.

Open
#12,066 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description
Swagger-codegen version
Swagger declaration file content or url
Command line used for generation
Steps to reproduce
Related issues/PRs
Suggest a fix/enhancement

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 collecting the missing Swagger-codegen version, declaration, generation command, and reproducible steps; the issue currently provides none of these. Compare the generated RestTemplate client with the reported HttpClient or socket behavior, and consider the work complete only when a reproducible generated client can send custom headers without the reported 400 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.