Error During Proxy Negotiation
vinukonda about 2 years ago Hi, I am a newbie. I have installed the server as well as the PSI client as per the user guide. I am trying to use the "localhost" as the virtual hosts. However I am getting the following error when connecting from the psi client. "There was an error communicating with the server.Details: Stream Negotiation Error: Host unknown". root@kumar-eME443:/usr/local/Tigase-5.2.0-b3447# more etc/init.properties --comp-class-1 = tigase.muc.MUCComponent--virt-hosts = localhost--user-db-uri = jdbc:mysql://localhost/tigasedb?user=tigase&password=tigase12--user-db = mysql--admins = admin@localhost--comp-name-4 = message-archive--comp-name-3 = proxyconfig-type = --gen-config-def--comp-name-2 = pubsub--comp-name-1 = muc--cluster-mode = true--sm-plugins = +message-archive-xep-0136,+jabber:iq:auth--debug = server--comp-class-4 = tigase.archive.MessageArchiveComponent--comp-class-3 = tigase.socks5.Socks5ProxyComponent--comp-class-2 = tigase.pubsub.PubSubComponent root@kumar-eME443:/usr/local/Tigase-5.2.0-b3447# more etc/tigase.conf #osgiEnabled=(true|false)#osgiEnabled=falseOSGI=trueENC="-Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8" DRV="-Djdbc.drivers=com.mysql.jdbc.Driver:org.postgresql.Driver:org.apache.derby.jdbc.EmbeddedDriver" #GC="-XX:+UseBiasedLocking -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:ParallelCMSThreads=2 -XX:-ReduceInitialCardMarks" #EX="-XX:+OptimizeStringConcat -XX:+DoEscapeAnalysis -XX:+UseNUMA" JAVA_HOME="/usr/lib/jvm/java-7-oracle" CLASSPATH="" JAVA_OPTIONS="${GC} ${EX} ${ENC} ${DRV} -server -Xms100M -Xmx200M -XX:PermSize=32m -XX:MaxPermSize=256m -XX:MaxDirectMemorySize=128m " TIGASE_CONFIG="etc/tigase.xml" TIGASE_OPTIONS=" --property-file etc/init.properties " Can someone help me in root causing the problem. Logs have nothing in them. Thank you in advance. Kumar Replies (5) RE: psi client not connecting - Added by Artur Hefczyc about 2 years ago Are you sure you used 'localhost' as a domain for your user account in Psi? RE: psi client not connecting - Added by kumar vinukonda about 2
hi everybody, i have just installed my first ejabberd, works great. i understand it comes bundled with http poll which is my specific interest at the moment. im trying to understand the inside of http poll, not just the concept of it but the protocol and what actually goes thru the wire. read thru the jabber jep-0025 http poll documentation, not much in there, so started reading the xmpp rfc 3920 and 3921, a bit too much in there. does anyone know of any documentation like 'xmpp protocol for dummies' kind of thing with reference https://projects.tigase.org/boards/15/topics/3067 to http poll. like: what does the http poll client send to the server to login what comes back, and so on. still reading the rfcs and trying to make heads or tails of it, but if anyone can point me to a simpler documentation, much appreciated. tia, nazri shuib Login or register to post comments If you just want to https://www.ejabberd.im/node/94 see what Submitted by mfoss on Wed, 2005-02-09 16:19. If you just want to see what are the messages exchange between client and server, you only need a Jabber client with http-poll capability that allows you to see raw XML (like Tkabber, Psi, Exodus...). This way you can see XML messages on live, while you use the client. » Login or register to post comments hi badlop, thx for the rep Submitted by mnshuib on Thu, 2005-02-10 15:47. hi badlop, thx for the reply. i hv installed ejabberd with http-poll. i can go to web admin at localhost:5280. web browser at localhost:5280/http-poll/ returns an empty xml string. so i assume the http-poll is running. i hv psi running and can connect direct to localhost:5222. silly q: do i need to hv a web server running at port 80 or can psi connect direct to localhost:5280? i cannot find much info on the http-poll setup. i tried setting up psi to go http-poll host=localhost port=5280 url=http-poll but keep getting error during proxy negotiation. im not getting the setup correct. tried changing url to localhost:5280/http-poll but still same error.
Next message ] [ Previous message ] [ In reply to ] [ Next in thread https://curl.haxx.se/mail/archive-2009-02/0106.html ] [ Replies ] From: Brian J. Murrell
web page. We've all seen them - enter your username and password into fields on the web page and press the Submit or Login button. From the standpoint of the underlying technology, this is no different than submitting any other form - only the names of the fields distinguish them as login or password fields and the security mechanism is implemented within the web application. The next most common form is authentication via credentials passed in the HTTP message headers. There are a number of schemes, but we can consider them all together as HTTP Authentication. This form of authentication is built into the web browser and the web server based on RFCs related to the HTTP specification. From a performance testing perspective, the various HTTP Authentication schemes work very similarly. However, it can be useful to understand the context in which they are used, especially when the web admin or developers might throw around their specific names - so I break down the HTTP Authentication methods into these three groups: Basic and Digest - Basic is defined in the HTTP 1.0 specification and digest is defined in RFC 2069. These are most commonly used on Apache and other open-source web servers. Basic sends the username and password insecurely (Base64-encoded text). Digest encrypts the password using an MD5 hash. NTLM and Negotiate (RFC-4559) is most commonly used on Microsoft IIS web servers. NTLM can be used exclusively, but modern servers typically use Negotiate to select which scheme will be used. The result is usually NTLM, but could also be Kerberos (or other yet-to-be-defined schemes). Proxy Authentication is defined in the HTTP 1.1 specification. This method is used by proxy servers when access to the proxy requires authentication. It may use any of the above schemes and operates in the same manner. However, it uses different headers to indicate to the browser that a proxy is requesting authentication, rather than the target server. How they work In all of these methods, the process begins when the browser requests a URL. If the URL requires authentication, the server returns a 401 response to the browser (or a 407 for a proxy server requesting authentication): Example of a 401 response from a server requesting authentication via the Basic method In the above example, the server has requested authentication using the WWW-Authenticate header. In that header, it indicates the scheme to be used to send the authenticat