Multiple modifications to a single request

[gregsdennis]

I have a set of requests on which I need to run multiple rules:

• redirect a server to my local
• add a header

I have both of these working as individual rules, but I can't seem to figure out how to put them together. The AI assistant says I can add a new condition to a rule, but it appears I can only add the same type of condition (e.g. only another redirect condition in the redirect rule).

I need to be able to do both of these because the Authorization header is being removed from redirects recently.

Thanks for the help.

[sachinjain024]

@gregsdennis Are you on the chrome extension or desktop app?

We recently made a change in the desktop app - requestly/requestly-desktop-app#214 and we no longer proxy the requests sent from the API client in the desktop app.

We thought it was un-necessary and overkill for proxying all the requests. Not sure if this is something that is related to what you are facing.

[gregsdennis]

I'm in the chrome extension, as my purpose is redirecting requests in our web app from the deployed API to my local machine. The redirect still occurs, but with recent changes, the Authorization header is no longer forwarded.

As a feature, though, the ability to perform multiple kinds of modifications on a single request seems essential. I see it as a single condition triggers a pipeline of modifications.

[wrongsahil]

Hey @gregsdennis

For adding multiple modification on request, it is possible by creating multiple rules.
Eg:

• Redirect https://example1.com -> http://localhost:5174/api/echo
• Then ading Request header on http://localhost:5174 using Header Rule

[wrongsahil]

For the Authorization header not redirecting issue

• This was fixed by adding a custom implementation to handle this specific case. Link to previous issue.
• The issue you provided specifically applies for requests that fires from Service Worker

Attached Screenshot for replication of Auth automatically adding to redirected request

Questions

• How are you trying to hit the url which needs to be redirected? (1 caveat i see is that the custom implementation can add the auth header automatically only on HTML pages as it relies on patching XHR and fetch)
• Possible to share production URL where i can test this behaviour?

For getting unblocked currently, you can add a custom authorization header on the redirected url using the Headers Rule

[gregsdennis]

For adding multiple modification on request, it is possible by creating multiple rules. - @wrongsahil

I did this first, and only one rule activates. The conditions are the same, and only the redirect actually does anything. Even so, how do I add a header when I don't know what the header value is? The header value I need is on the original request.

You show the results of it working for you, but provide nothing as far as how to set this up.

How are you trying to hit the url which needs to be redirected?

What? This is a web page trying to hit a URL. I've already explained that I'm trying to redirect a request headed to a deployed server to my local. This is a private test environment URL. I'm sure you can test with any authenticated call that a web page makes.

[gregsdennis]

Now it's just working again.

[wrongsahil]

We didn't change anything 😓. @gregsdennis, if you face this issue again, please let me know. We can schedule a call to resolve it quickly.

[gregsdennis]

@wrongsahil I figured out that this is specifically breaking when running in incognito mode. It works when running normal mode.