-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy with certificates #17
Comments
A new configuration option is needed |
Suggested configuration: {
"name": "rbowen",
"root": "build/",
"port": 4000,
"proxy": {
"/api": {
"url": "http://10.0.16.227:8080/ebd-rest",
"key": "/path/to/key.pem",
"cert": "/path/to/cert.pem"
}
}
}
|
Test with custom server: |
openssl genrsa -out ca.key 4096
openssl req -x509 -new -nodes -key ca.key -days 999 -out ca.pem
openssl genrsa -out server.key 1024
openssl req -new -key server.key -out server.csr
openssl x509 -req -days 999 -in server.csr -CA ca.pem -CAkey ca.key -out server.pem
openssl genrsa -out client.key 1024
openssl req -new -key client.key -out client.csr
openssl x509 -req -days 999 -in client.csr -CA ca.pem -CAkey ca.key -out client.pem |
I've created an issue to node-http-proxy http-party/node-http-proxy#826 |
More examples! https://github.com/coolaj86/nodejs-ssl-example |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now, when you configure the proxy to an url with needs a certificate, always response a 403.
If you install the certificate in the browser, you can reach the url, but with freddie response a 403
The text was updated successfully, but these errors were encountered: