bug: Request intercepted but not showing up when initiated from Requestly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- express, javascript, typescript
- Domain
- desktop, devtools, networking
Research direction
Start by reproducing the difference in the Requestly Desktop App using the listed proxy, curl/browser requests, and the Requestly-initiated request. Compare why the intercepted 500 response appears but the request is absent from the list; done means the Requestly request is recorded while the existing interception rule still works.
Written by the indexing model from the issue text.
Description
Describe your issue?
I have a simple Express app on localhost:3000/httpbin that hits httpbin.org
// Third-party API call to httpbin
app.get('/httpbin', async (req, res) => {
try {
const response = await axios.get('https://httpbin.org/get');
res.json(response.data);
} catch (error) {
res.status(500).json({ error: 'Failed to fetch from httpbin', details: error.message });
}
});
I'm trying to intercept this call and replace it with a 500 response. I have set up the proxy in my terminal where the app is running. I have the rule set up.
If I do curl localhost:3000/httpbin, I can see it works.
However, if I hit the same endpoint through Requestly, the rule still works (because I can see 500 error), but it doesn't show up in the list.
I'm extremely confused. Both are making requests to localhost:3000/httpbin, so why is one showing up and not the other? I can also open localhost:3000/httpbin on my browser and it also records the URL.
Repro steps
- Set up proxy.
- Run npm start
- Make request via curl or browser - works
- Make request via Requestly - does not work.
What Requestly tool were you using?
- Extension
- Desktop-App
- Android SDK
- Selenium
Your Environment
Windows 11
Requestly Version
25.8.29
Error screenshot
No response
- Dominant language
- TypeScript
- Stars
- 87
- Forks
- 23
- Avg merge
- 14h
- Merged PRs (30d)
- 3
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.
More from requestly/interceptor
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
requestly/interceptor#121 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
requestly/interceptor#26 · 1 comment ·
-
migration:misfiled-interceptor
Difficulty 5/5 Over a week Newbie friendliness 38/100
requestly/interceptor#27 · 2 comments ·
-
migration:misfiled-interceptor
Difficulty 3/5 1-2 days Newbie friendliness 45/100
requestly/interceptor#28 · 1 comment ·
-
migration:misfiled-interceptor type:bug
requestly/interceptor#29 · 2 comments · 1 assignee ·
All issues in requestly/interceptor
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·