Open aeife opened 10 years ago
I'm dealing with a similar issue right now, only it's an IIS server and NTLM. From what I've been able to gather, this is something that's added to the request during the handshake with the proxy server, and would require further middleware to support.
gulp-webserver proxies.options
support any options available from connect-proxy, which in turn implement the options supported by http
and https
I believe we'd have to do a transform on the initial handshake response from the server to include the required authentication in both of our cases.
Hi!
I'm using gulp-webserver for my AngularJS application. In production my application is served via apache which proxies incoming requests to various locations.
To prevent my client from knowing the api key the apache proxy also adds an authorization header with the api key to each request. Is this somehow possible with gulp-webserver or what is the recommended solution for this?