Open GoogleCodeExporter opened 8 years ago
configure:
"PROXY_SERVER":
{
"ADDRESS": "",
"PORT": 0,
"AUTHENTICATION":
{
"USERNAME": "",
"PASSWORD": ""
}
}
Original comment by jeroen.v...@gmail.com
on 20 Feb 2013 at 2:38
I had configured it!my proxy server:10.0.0.1,port:8080
The proxy server can't resolve "appname.rhcloud.com".
Original comment by linktest...@gmail.com
on 20 Feb 2013 at 2:47
Your address is XXX–YYY.rhcloud.com?
Your port is 8000 (HTTP) or 8443 (HTTPS)?
You can open http://XXX-YYY.rhcloud.com in your browser (blanco page)?
Original comment by jeroen.v...@gmail.com
on 20 Feb 2013 at 3:04
Your address is XXX–YYY.rhcloud.com? YES
Your port is 8000 (HTTP) or 8443 (HTTPS)? 8443
You can open http://XXX-YYY.rhcloud.com in your browser (blanco page)? YES I
Can.blank page.
CHINA GFW Block It(DNS) ?
Original comment by linktest...@gmail.com
on 20 Feb 2013 at 3:39
I do not live in china, so I can not test GFW.
Can you attach your logs?
Original comment by jeroen.v...@gmail.com
on 20 Feb 2013 at 6:15
[deleted comment]
[deleted comment]
sorry,I can't open http://XXX-YYY.rhcloud.com,but I can open
https://XXX-YYY.rhcloud.com in firefox or chrome(blank page).
"HTTP 400 ERROR" IN IE.
C:\JAP>JAP_WS_LOCAL.exe
DEBUG:JAP.JAP_LOCAL:InputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: phx-sync461.services.mozilla.co
m
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: phx-sync461.services.mozilla.co
m
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: www.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: sb-ssl.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionMade
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState0
DEBUG:JAP.JAP_LOCAL:InputProtocol.dataReceived
DEBUG:JAP.JAP_LOCAL:InputProtocol.processDataState1
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddressType: 3
DEBUG:JAP.JAP_LOCAL:InputProtocol.remoteAddress: sb-ssl.google.com
DEBUG:JAP.JAP_LOCAL:InputProtocol.remotePort: 443
DEBUG:JAP.JAP_WS_LOCAL:WSInputProtocol.do_CONNECT
DEBUG:JAP.JAP_WS_LOCAL:WSOutputProtocolFactory.__init__
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
DEBUG:JAP.JAP_LOCAL:InputProtocol.connectionLost
Original comment by linktest...@gmail.com
on 21 Feb 2013 at 6:54
[deleted comment]
{
"LOGGER":
{
"LEVEL": 10
},
"LOCAL_PROXY_SERVER":
{
"ADDRESS": "127.0.0.1",
"PORT": 1080
},
"REMOTE_PROXY_SERVERS":
[
{
"TYPE": "HTTPS",
"ADDRESS": "xxx-xxx.rhcloud.com",
"PORT": 8443,
"AUTHENTICATION":
{
"USERNAME": "xx",
"PASSWORD": "xx"
},
"CERTIFICATE":
{
"AUTHENTICATION":
{
"FILE": ""
}
}
}
],
"PROXY_SERVER":
{
"ADDRESS": "10.0.0.1",
"PORT": 8080,
"AUTHENTICATION":
{
"USERNAME": "",
"PASSWORD": ""
}
}
}
Original comment by linktest...@gmail.com
on 21 Feb 2013 at 7:34
As far as I can see, your configuration is correct.
Does your proxy server support HTTP CONNECT Tunneling
(http://en.wikipedia.org/wiki/HTTP_tunnel#HTTP_CONNECT_Tunneling)?
Original comment by jeroen.v...@gmail.com
on 21 Feb 2013 at 6:52
Maybe you're right!Is there a tool to check HTTP CONNECT Tunneling?
Original comment by linktest...@gmail.com
on 24 Feb 2013 at 7:37
I have tried most of the proxies in
http://spys.ru/free-proxy-list/CN/
none was work as a father proxy of JAP.you can test it too.
does the proxy function work?
Original comment by westmin...@gmail.com
on 25 Feb 2013 at 3:41
You can try software like http://www.proxifier.com/
Original comment by jeroen.v...@gmail.com
on 25 Feb 2013 at 8:11
I use Archlinux.Proxifier has no linux version.
So i use privoxy with this series of setting
browser -> JAP -> privoxy -> father proxy -> website
Not work.
I think JAP will NOT send data to father proxy correctly,so need some
application like proxifier to hijack the data to send.
Original comment by westmin...@gmail.com
on 27 Feb 2013 at 5:19
JAP 2.0.0 only supports HTTP proxies.
Are the other proxies HTTP proxies?
Original comment by jeroen.v...@gmail.com
on 27 Feb 2013 at 6:56
Yes.I pick up working http proxies from http://spys.ru/free-proxy-list/CN/
without JAP to test them.
Original comment by westmin...@gmail.com
on 28 Feb 2013 at 12:37
Original issue reported on code.google.com by
linktest...@gmail.com
on 20 Feb 2013 at 11:57