You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.
After upgrading a project from version 3.0.0 to version 3.1.2 of vueclimiddleware, I get the following response when accessing the app via its reverse proxy URL at https://localhost:/ with an HTTP 200 status:
<HTML><TITLE>Forbidden</TITLE><H1>Self-referential requests to proxy are forbidden</H1>Self-referential requests to this proxy server are forbidden</HTML>
Steps to reproduce
I reproduced this problem on Windows 10 2004, .NET Core 3.1
Being behind a corporate proxy, I have set the environment variables HTTP_PROXY=http://<proxy>:<port> and NO_PROXY=localhost .
Start the sample app in /samples/VueCliSample in this repo.
The problem is caused by .NET Core 3.1 apparently ignoring the NO_PROXY variable and probably needs to be fixed by the .NET team where a similar issue is tracked for the Angular middleware (dotnet/aspnetcore#14392).
As a workaround, the HTTP_PROXY can be unset in the launchSettings.json file:
Problem description:
After upgrading a project from version 3.0.0 to version 3.1.2 of vueclimiddleware, I get the following response when accessing the app via its reverse proxy URL at https://localhost:/ with an HTTP 200 status:
<HTML><TITLE>Forbidden</TITLE><H1>Self-referential requests to proxy are forbidden</H1>Self-referential requests to this proxy server are forbidden</HTML>
Steps to reproduce
I reproduced this problem on Windows 10 2004, .NET Core 3.1
HTTP_PROXY=http://<proxy>:<port>
andNO_PROXY=localhost
./samples/VueCliSample
in this repo.The browser opens at https://localhost:44323/ and displays the error message from above.
Workaround
The problem is caused by .NET Core 3.1 apparently ignoring the
NO_PROXY
variable and probably needs to be fixed by the .NET team where a similar issue is tracked for the Angular middleware (dotnet/aspnetcore#14392).As a workaround, the
HTTP_PROXY
can be unset in thelaunchSettings.json
file:I'd suggest adding this to the documentation / wiki as a know issue
The text was updated successfully, but these errors were encountered: