Skip to content
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.

pac file limitation #63

Closed
itskeKs opened this issue Mar 5, 2017 · 15 comments
Closed

pac file limitation #63

itskeKs opened this issue Mar 5, 2017 · 15 comments

Comments

@itskeKs
Copy link

itskeKs commented Mar 5, 2017

Hello @zhuhaow,

i am running into some issues when i am using a pac file within NEKit on iOS 10.2.1. I dont know if it is related to NEKit or an Apple limitation but maybe you can help.

proxySettings.autoProxyConfigurationEnabled = true
proxySettings.proxyAutoConfigurationJavaScript = local.pacJSCode()
//proxySettings.proxyAutoConfigurationJavaScript = nil
//proxySettings.proxyAutoConfigurationURL = URL(string: "https://some/address/to/pac.js")

The error appears on both versions of code (local or remote pac). If i send a lot of requests either from an App or from Safari i have some kind of loading hang. It starts to load then the loading freezes and it takes the system something like 10-20s to load further.

For clarification: the pac file forwards to the proxy running on port 9090 so thats nit the issue. Requests are also forwarded to remote server when i am sing one.

Thanks for any help you can provide.

Best,

keKs

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

There's a bug when safari connects a https site through proxy, it will pretend it is reading from the remote even if the connection is broken.
I do not know if this is the case or what you settings are.
Hope that helps.

@zhuhaow zhuhaow closed this as completed Mar 5, 2017
@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

hmm i dont think thats the issue here. since when i do not use the pac file everything works just fine. it looks more like there is something wrong within requests handling when pac file is used. when i open something what makes a lot of requests the requests kind of stop for a couple of seconds (some apps throw connection error) but then it starts loading again. i dont understand why this happens :|

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

Since the details are as vague as possible, I really can't tell what happens.
Do you enable TUN interface and route DNS request to NEKit?

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

tun interface is disabled. dns requests are routed to nekit. the pac file contains a blacklist of hosts which are blocked. they get redurected to nginx with a 502 error so the system knows what to do.

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

Eh, you can't route dns requests to NEKit without enabling tun interface.

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

then i dont get it. so it is disabled then.

how can i check actually?

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

You can paste your code here.

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

which part of code? :)

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017 via email

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

...

1 similar comment
@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

...

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

Whatever is wrong with PAC has nothing to do with NEKit.

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

ok :(

@itskeKs
Copy link
Author

itskeKs commented Mar 5, 2017

@zhuhaow which remote SS version does NEKit support? i am using ss 2.9.1 i think the issue might be here.

@zhuhaow
Copy link
Owner

zhuhaow commented Mar 5, 2017

Don't know.
If you can successfully connect to one host through ss proxy I don't think a lot simultaneous connections would make any difference.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants