Closed ryanhugh closed 1 year ago
Hi, is this still an issue for you with the newest version of the plugin?
No idea, due to other reasons I don't have to attach this header anymore
Thank you!
On Mon, May 22, 2023 at 7:52 AM, Luca Forstner < @.*** > wrote:
Hi, is this still an issue for you with the newest version of the plugin?
— Reply to this email directly, view it on GitHub ( https://github.com/getsentry/sentry-webpack-plugin/issues/416#issuecomment-1557080679 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/ABMCUS3CZTV66OXKFJPQ77LXHNHOFANCNFSM6AAAAAAS56EN3Y ). You are receiving this because you authored the thread. Message ID: <getsentry/sentry-webpack-plugin/issues/416/1557080679 @ github. com>
Environment
What version are you running? Etc.
@sentry/webpack-plugin v1.20.0
Steps to Reproduce
Expected Result
It should send the custom header. It does send the customer header when I set the CUSTOM_HEADER env var, so I'm not blocked on this bug.
Actual Result
It doesn't work with field:
It works with env var: