Skip to content
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

No support Self-signed certificate #207

Closed
631068264 opened this issue Dec 9, 2021 · 1 comment
Closed

No support Self-signed certificate #207

631068264 opened this issue Dec 9, 2021 · 1 comment

Comments

@631068264
Copy link

0. Before Your ASK

  1. Try to find an answer by reading a FAQ.

Ⅰ. Issue Description

I config a forward proxy to connect a self-signed certificate url use

curl -k xxx:8080 https://xxxx

Ⅱ. Describe what happened

Get 503 response

Ⅲ. Describe what you expected to happen

Get the same result as

curl -k https://xxxx

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?

  1. If applicable, add nginx debug log.

Ⅵ. Environment:

  1. Tengine/Nginx/OpenResty version (use sbin/nginx -v):
  2. Which patch do you use?
@chobits
Copy link
Owner

chobits commented Jan 28, 2022

use curl -x option for HTTPS tunnel. The request of your curl is handled by original nginx module(HTTPS module), not by this module(proxy_connect module).

@chobits chobits closed this as completed Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants