Topazstix / sandrop

Automatically exported from code.google.com/p/sandrop
0 stars 0 forks source link

Bug - Fetching new script. Existing not valid!!! #115

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Setup the proxy in Script approach for both WIFI and NOT LISTED mode, with 
URL http://chieko.kwik.to/proxy.pac
2.The mobile switch to 3G mode, the NOT LISTED mode activated, and works well.
3.Move the phone into the WIFI range, the WIFI activated, and the Drony switch 
to WIFI mode;

What is the expected output? What do you see instead?

The script was saved and not modified, so the program shouldn't say the script 
is not valid. But the log prints "Fetching new script. Existing not valid!!!" 
and then the proxy failed.

What version of the product are you using? On what operating system?

Drony v1.2.82, on Android 4.3

Original issue reported on code.google.com by janvier....@gmail.com on 18 Jan 2015 at 4:54

GoogleCodeExporter commented 8 years ago
Will look at it and let you know. Sorry for late response

Original comment by supp.san...@gmail.com on 23 Jan 2015 at 6:52

GoogleCodeExporter commented 8 years ago
I found the reason of reporting the script not valid by the app - the script is 
still there and nothing changed, but marked as EXPIRED by the default value 
(3600s) of Script Cache Timeout. Use case:

1. Setup the script on a specified Wi-Fi;
2. Set the Wi-Fi proxy to localhost:8020 in Android system;
3. Everything goes well. The problem is not here.
4. One hour (3600s) later, the script expired;
5. Drony gives up the existing script in cache, and try to fetch a new one;
6. BUT, Wi-Fi has proxied the traffic to localhost:8020, it means the traffic 
is routed to Drony;
7. Drony received the request, and found (again) the existing script has 
expired; fetch it again... and again... it is a death loop.

My workaround approach is set both Script Cache Timeout and Script Fetch 
Interval to a very long time, everything goes well so far. But it still a bug 
and hope you can find a way to fix this issue.

Original comment by janvier....@gmail.com on 23 Jan 2015 at 7:41

GoogleCodeExporter commented 8 years ago
Please try latest version on Google Play. It should fix the problem

Original comment by supp.san...@gmail.com on 27 Jan 2015 at 5:20

GoogleCodeExporter commented 8 years ago
Thanks for your effort and dedication. As I tested, it's partial fixed. My 
scenario is a bit complex than the previous case:

1. I have Wi-Fi A in my home
2. I have 3G connection when leaving home
3. I have Wi-Fi B in office

I setup the auto-proxy script for Wi-Fi A, Wi-Fi B and "NOT LISTED" in Drony.

Everything works good last night, and this morning when I back to office, I 
found the connection (connected to Wi-Fi B) is broken. Then I entered the Drony 
and check the log, and found "Existing not valid" again. Maybe the problem is 
in the switching modes of Wi-Fi / NOT LISTED / Wi-Fi, I guess.

Original comment by janvier....@gmail.com on 28 Jan 2015 at 2:34

GoogleCodeExporter commented 8 years ago
You have the same script for all networks?
It is stored locally or on some http site? Fetch should happen after fetch 
interval.
But will test more to be shure that this works okey.

Original comment by supp.san...@gmail.com on 30 Jan 2015 at 9:54

GoogleCodeExporter commented 8 years ago
Never tested these two settings anymore because I had set them to a very large 
number.

I can do a test again but Drony does not work on my Android 5.1.0 anymore. :( 

Original comment by janvier....@gmail.com on 18 Mar 2015 at 1:45

GoogleCodeExporter commented 8 years ago

Can not test, but will get 5.1 on nexus 5 probably soon. Will try to fix it 
asap.
You can send some screenshots even before. Maybe it will show something 
interesting.

Original comment by supp.san...@gmail.com on 18 Mar 2015 at 3:59