If anyone else can help, please do so. I am willing to compensate for the time spent on resolving this problem. I have been trying to fix it for a while, whenever i disable http-binding from the admin panel, http://localhost:8080/http-bind/ doesn’t work, but when I enable it, it gives me a 404 Error. Anyway to fix this?
I checked again with our OF server - try the address http://localhost:8080 - that should give you something about http binding, adding the alias does give me a 404 too.
I get the same 404 “NOT FOUND” error in my browser, When I go to http://localhost:8080/ using Openfire 3.4.2
I downgrade my version to Openfire 3.4.1 and now when i go to http://localhost:8080/ , i can see a webpage that says http-binding. I could also configure a /jwchat and a /jeti directories, just copying the files under the \resources\spank subdirectories in Openfire Home, then i get some http services from there (Openfire in this case works like a Web Server i didn´t need Apache or Tomcat)
Apparently, 3.4.1 and prior versions do not give this error, only the new versions do. And I am pretty sure the HTTP Binding is enabled, it just doesnt say anything. Let me know if this is correct.
I do not know whether this is the correct answer or not but, apparently it works if an XMPP request is sent to it, but not an HTTP request. Which I think makes no sense because it is an HTTP BIND, so it should be responsive to HTTP requests. I think it might be a major bug that we should maybe report?
You need to be posting data (<body …></body>) according to the XMP Protocol in order not to get a 404 on this page. According to the protocol, I believe the 404 error indicates that you’re not providing an sid/rid and/or not trying to authenticate. So you get the NOT_FOUND 404 page.
finally I got jwchat running. At least the roster is loaded, the buttons arent working, but thats not related to our http-bind problem.
So what did I do?
Working with jwchat1.0B3 I deleted all language-files and renamed the *.html.html and *.js.js to *.html and *.js So as a result the jwchat directory just contains *.html and *.js files
Afterwards I changed my Virtualserver settings and made sure that following commands are used in this order.
I guess thats what Ive done. So try to connect via jwchat. You will see the http-binding is working, though an error message is thrown by jetty sending an http-request to the socket.