Automattic / Automattic/wpcom-xhr-request
Missing normalization for proxyOrigin attribute
Open
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
If we try to set the proxy origin URI with a trailing slash at the end, fetching data will fail since the normalization for that attribute is missing. #35
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the proxyOrigin attribute is handled and compare it with any existing URI normalization in the request path. Reproduce the trailing-slash case, then verify that fetching data succeeds when proxyOrigin includes a trailing slash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100