spring-cloud / spring-cloud/spring-cloud-gateway
If the input parameter contains special characters such as brackets and Use url to access the service directly instead of through the default load balancing。 the parameter will encode and I have to decode myself
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
If the input parameter contains special characters such as brackets
and Use url to access the service directly instead of through the default load balancing。
the parameter will encode and I have to decode myself。
but it's ok if I visitor service by through the default load balancing。
springboot version 2.1.4.RELEASE
springcloudversion Greenwich.SR1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the parameter-encoding difference between direct service access and the default load-balancing path using Spring Boot 2.1.4.RELEASE and Spring Cloud Greenwich.SR1. Compare the resulting request parameters and identify the gateway entry point involved; done means special characters such as brackets remain consistent without manual decoding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100