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

questions about using autoproxy setting #21

Open
hy05190134 opened this issue Feb 14, 2019 · 2 comments
Open

questions about using autoproxy setting #21

hy05190134 opened this issue Feb 14, 2019 · 2 comments

Comments

@hy05190134
Copy link

I find that the content of "http://localhost:1270/proxy.pac" just will proxy to localhost:1270, but when I test the https://xxx.com, it will throw some error because client proxy to 1270 which should be 8443 by default, so the proxy.pac can't proxy http and https simultaneously?

another question:

even when I proxy to 8443 port, and the proxy also throw some error for tls connection when handshake like this:

"http: TLS handshake error from 127.0.0.1:63238: tls: oversized record received with length 20037"

@hy05190134
Copy link
Author

using macOs and safari

@Mudassir55
Copy link

The proxy auto-config (PAC) file at "http://localhost:1270/proxy.pac" is a JavaScript file that defines the proxy configuration for client devices. The configuration specifies the URL or IP address of the proxy server to use for different types of network traffic, based on the URL or IP address of the destination.

In your case, the PAC file is specifying that all traffic should be sent to "localhost:1270", which is the default proxy configuration. This would work for HTTP traffic, but it would likely not work for HTTPS traffic because the default port for HTTPS traffic is 443, not 1270.

As for the error message you encountered when trying to use the proxy server for HTTPS traffic, "tls: oversized record received with length 20037", it suggests that there might be a mismatch between the encryption settings of the client and the proxy server. This could be due to a configuration issue with the proxy server, or it could be a result of network limitations or interference.

You may want to check the configuration of your proxy server and ensure that it is properly configured to support HTTPS traffic. You should also check your network infrastructure to ensure that there are no firewalls or other security measures that are blocking or interfering with the HTTPS traffic.

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