Redirection location method not GET

[ElRige]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying

Bruno version

2.0.1, 2.1.0

Operating System

macOS 15.3.2

Describe the bug

With a request like POST /resources
If the response is HTTP 303 with header location "/resources/1234"
Bruno try to call POST "/resources/1234" and failed because there is no such path
Bruno should call GET "/resources/1234"

.bru file to reproduce the bug

No response

Screenshots/Live demo link

failed with redirect :

303 when no redirect :

[mlataza]

I'm having the same issue.

[anusree-bruno]

Hey! Thanks for reporting this issue. I've looked into how HTTP redirects should work, and here's what I found:

1. What's happening now in Bruno:

• Bruno keeps the original method (like POST) for all redirects
• This causes problems with 301, 302, and 303 redirects

2. What the HTTP spec says:

• 301/302: Can change POST to GET (but doesn't have to)
• 303: Should use GET or HEAD
• 307/308: Must keep the original method

3. How it should work:

Status Code	What happens	Body handling
301	- HEAD stays as HEAD - Everything else becomes GET	TBD
302	- HEAD stays as HEAD - Everything else becomes GET	TBD
303	- HEAD stays as HEAD - Everything else becomes GET	TBD
307	Keep whatever method was used	Keep the body
308	Keep whatever method was used	Keep the body

4. Things we need to decide:

• Should we keep or remove the request body when changing to GET?
• Should we add an option to let users choose whether to keep the original method?

You can check out the full spec here: https://datatracker.ietf.org/doc/html/rfc7231#section-6.4

[ElRige]

I didn't make it clear in my first post, in previous versions of Bruno (1.x.x and 2.0.0), the redirection worked fine.
So version 2.0.1 has created a regression

[anusree-bruno]

@ElRige
Earlier axios was handling the redirects we had changed it here #4324. I think axios was handling these scenarios.

[ramki-bruno]

Axios internally uses follow-redirects to handle the redirects.
https://github.com/axios/axios/blob/5064b108de336ff34862650709761b8a96d26be0/lib/adapters/http.js#L435-L450
And below is the logic used within
https://github.com/follow-redirects/follow-redirects/blob/694d6b47a42bc8377e5ef1480394de451e16bd5b/index.js#L437-L450
which is not exactly same as

bruno/packages/bruno-electron/src/ipc/network/axios-instance.js

Lines 316 to 324 in e7dd78e

	// For 301, 302, 303: change method to GET unless it was HEAD
	if ([301, 302, 303].includes(statusCode) && originalMethod !== 'head') {
	requestConfig.method = 'get';
	requestConfig.data = undefined;
	delete requestConfig.headers['content-length'];
	delete requestConfig.headers['Content-Length'];
	delete requestConfig.headers['content-type'];
	delete requestConfig.headers['Content-Type'];