Authorization header is not passed with Redirect Request or Replace String

Open
#71 3 comments 1 reaction 1 assignee View on GitHub

@nsrCodes is already working on this.

Since Mar 15, 2024.

Assessment

This issue has not been assessed yet.

Description

bug

Prerequisites

  • Using the latest version of Requestly

Expected Behavior

When I am creating a 'Redirect Request' or 'Replace String' HTTP Rule in the Desktop App it should forward/redirect to the changed endpoint URL. All original header keys and values should be passed.

Current Behavior

All original header keys and values are being passed, except the 'Authorization' header. The 'Authorization' header vanished.

Steps to Reproduce

  1. Open the Requestly Desktop-app.
  2. Create Redirect Rule (or a Replace String rule) to forward the request to another endpoint (staging api for example)
  3. Use any http request with an 'Authorization' header.
  4. The 'Authorization' header has vanished.

Possible Solution (Not obligatory)

This was also an issue on the Chrome plugin:
https://github.com/requestly/requestly/issues/1208

I noticed that this (https://github.com/requestly/requestly/issues/1208#issuecomment-1801505984) workaround fixed my issue as well for the Desktop Application !

Context

I tested this by sending requests to an PHP file with the following code to see all headers:
$headers = getallheaders(); var_dump($headers);

  1. 'Replay request' with the Authorization header:
    You can see the Authorization header vanished
example_1
  1. 'Replay request' with the Authorization header + Authorization2 header:
    You can see the Authorization header vanished, but the Authorization2 header did not.
example-2
  1. 'Replay request' with the Authorization header and this (https://github.com/requestly/requestly/issues/1208#issuecomment-1801505984) workaround applied:
example-3

Your Environment

  • Operating System and version : Windows 11 23H2
Dominant language
TypeScript
Stars
160
Forks
60
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from requestly/http-interceptor-desktop-app

All issues in requestly/http-interceptor-desktop-app

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.