microsoft / microsoft/aspire

Devtunnel no longer forwarding Authorization header from source

Open
#14,298 0 comments 0 reactions 0 assignees View on GitHub
devtunnels
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

The Aspire devtunnel resource behavior seems to have changed. I have a webhook where I configure an Authorization header value for the source to send along to an anonymous webhook for local development purposes (think of it as an API Key). This header is no longer making it from the devtunnel to my local environment when previously the Authorization: Bearer value was available.

Version Aspire.Hosting.DevTunnels v13.1.0

### Expected Behavior

The header to be passed along.

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version info

_No response_

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the Aspire.Hosting.DevTunnels v13.1.0 implementation and trace how source request headers are forwarded to the local webhook. Reproduce the webhook setup described in the issue and verify that the configured Authorization: Bearer header reaches the local environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.