I’‘ve read various posts on the forum, about this issue, however none was able to solve mine! The problem persists, I’'ve tracked the http request and response and found out the following: jwchat creates an xmpp-http POST request, but openfire returns the default HTML page about “Openfire HTTP Binding Service”.
Post
Response
…etc… (I snipped the output, because it’'s what you get when you point your browser to the XMPP-HTTP-Bind URL)
I’‘ve added these fancy system properties and all, but I’‘m not able to get a real http binding response. Although I haven’‘t read the XEP-124 specification, so I’'m not sure what the response should be, but I guess something more xml-ish.
The issue appeared in Safari 3.0beta, Firefox (2.0.0.4, Mac & Linux), haven’'t tested it in IE though.
Hope somebody can enlight me, with a solution! Thanks in advance
from my client i can access http : // jabber.server.name/http-bind/ and get “Openfire HTTP Binding Service”. so reweite etc. works as expected. the relevant parts of my jwchat config look like this:
What does +Multiviews do? I tried looking in apache docs and it says it guesses the file name if its not supplied. It doesnt make sense to me. Is multiviews essential only for jwchat or for every javascript client?
Do you need to set RewriteEngine On and ProxRequests On? It might open unecessary security hole. A quote from apache docs: "A reverse proxy is activated using the directive or the flag to
the `` directive. It
[ProxyRequests|#proxyrequests]
is not necessary to turn `` on in order to configure a
reverse proxy"
Shouldn`t the reverse proxy direct to the the same url the request came from?
The Multiviews option automatically selects the right index.html, by using the language code that your browser submits. If the right language is not available, index.html.html is taken.
Thanks Coolcat. That explains what multiviews does.
Does anybody have an answer to my other questions:
Do you need to set RewriteEngine On and ProxRequests On? It might open
unecessary security hole. A quote from apache docs: “A reverse proxy is
activated using the <code>[#proxypass]</code> directive or the
<code>[P]</code> flag to
the <code>[RewriteRule|http://www.igniterealtime.org/mod/mod_rewrite.html#rewriterule]
directive. It
is not necessary to turn <code>[#proxyrequests]</code> on
in order to configure a
reverse proxy”
Shouldn`t the reverse proxy direct to the the same url the request came from?