Comments (17)
configure:
"PROXY_SERVER":
{
"ADDRESS": "",
"PORT": 0,
"AUTHENTICATION":
{
"USERNAME": "",
"PASSWORD": ""
}
}
Original comment by [email protected]
on 20 Feb 2013 at 2:38
from jap.
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 [email protected]
on 20 Feb 2013 at 2:47
from jap.
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 [email protected]
on 20 Feb 2013 at 3:04
from jap.
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 [email protected]
on 20 Feb 2013 at 3:39
from jap.
I do not live in china, so I can not test GFW.
Can you attach your logs?
Original comment by [email protected]
on 20 Feb 2013 at 6:15
from jap.
[deleted comment]
from jap.
[deleted comment]
from jap.
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 [email protected]
on 21 Feb 2013 at 6:54
from jap.
[deleted comment]
from jap.
{
"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 [email protected]
on 21 Feb 2013 at 7:34
from jap.
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 [email protected]
on 21 Feb 2013 at 6:52
from jap.
Maybe you're right!Is there a tool to check HTTP CONNECT Tunneling?
Original comment by [email protected]
on 24 Feb 2013 at 7:37
from jap.
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 [email protected]
on 25 Feb 2013 at 3:41
from jap.
You can try software like http://www.proxifier.com/
Original comment by [email protected]
on 25 Feb 2013 at 8:11
from jap.
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 [email protected]
on 27 Feb 2013 at 5:19
from jap.
JAP 2.0.0 only supports HTTP proxies.
Are the other proxies HTTP proxies?
Original comment by [email protected]
on 27 Feb 2013 at 6:56
from jap.
Yes.I pick up working http proxies from http://spys.ru/free-proxy-list/CN/
without JAP to test them.
Original comment by [email protected]
on 28 Feb 2013 at 12:37
from jap.
Related Issues (20)
- Jap Modulus Test
- [Tutorial] Connect to Minecraft on Openshift via JAP HOT 15
- JAP deploying on nodejitsu failed HOT 2
- JAP_REMOTE_WS_NODE_MODULUS HOT 23
- Openshift node error(Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE) HOT 3
- Fatal Error(JAP_LOCAL_PYTHON_WINDOWS) HOT 1
- executing problem HOT 10
- HTTP vs HTTPS HOT 4
- jap-remote-ws-python-openshift-3.0.0 file permissions HOT 1
- bug of "JAP_REMOTE_WS_NODE_NODEJITSU-3.0.0-SNAPSHOT-2"? HOT 8
- JAP_LOCAL_WS_PYTHON-3.0.0-SNAPSHOT-3 not working on linux HOT 6
- UDP cause JAP_LOCAL_WS_NODE-3.0.0-SNAPSHOT-2 crash HOT 4
- JAP_WS_PYTHON_OPENSHIFT-3.0.0 does not work HOT 1
- JAP_REMOTE_WS_NODE_OPENSHIFT-3.0.0 is not working
- Heroku | WebSockets Now in Public Beta HOT 14
- JAP_LOCAL_WS_PYTHON_WINDOWS-3.0.0 error HOT 3
- I hope HTTP can be encrypted.
- INSTALL_JAP_LOCAL_WS_PYTHON error HOT 1
- why JAP is slower than APJP
- How to install streamws in XP? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jap.