--
You received this message because you are subscribed to the Google Groups "Strophe" group.
To post to this group, send email to str...@googlegroups.com.
To unsubscribe from this group, send email to strophe+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/strophe?hl=en.
I just got Proxy with SSL working on my server by enabling the
SSLProxyEngine on
directive.
See [1], for a more complete config. Also see the SSLProxyXXXX
directives at [2].
Ilya
[1]
http://elsid.net/2007/08/31/how-to-get-apache-proxypass-working-with-ssl/
[2] http://httpd.apache.org/docs/2.2/mod/mod_ssl.html
Troy Steinbauer wrote:
> I will try again. I spent a few hours trying to get it to connect and
> kept failing. It must be the apache configuration.
>
> On a side note, Wikipedia's OpenFire
> <http://en.wikipedia.org/wiki/Openfire> page states that it
> can handle SSL connections, but not with self-signed certs. I only
> currently have access to self signed certs. However I do believe I
> found an option in the OpenFire configuration page that allows
> self-signed.
>
> On Fri, Jul 23, 2010 at 6:31 PM, Jamie Johnson <jej...@gmail.com
> <mailto:jej...@gmail.com>> wrote:
>
> I will have to double check our implementation on Monday morning
> but I am 95% sure we have successfully connected libstrope via
> https. If I remember correctly you need to ensure that you have
> your apache proxy forwarding requests for https to the openfire
> server and the page must also be served via https. Again I can
> double check Monday but I believe that is all we needed to do.
>
>
> On Fri, Jul 23, 2010 at 2:12 PM, Troy <troyste...@gmail.com
> <mailto:troyste...@gmail.com>> wrote:
>
> First question: Can Strophe.js handle HTTPS BOSH connection to
> OpenFire's port 7443?
>
> If so, has anyone had any successful attempts at this? I can get
> Strophe to connect to 7070 unsecured, but I must be doing
> something
> wrong in connecting to 7433.
>
> --
> You received this message because you are subscribed to the
> Google Groups "Strophe" group.
> To post to this group, send email to str...@googlegroups.com
> <mailto:str...@googlegroups.com>.
> To unsubscribe from this group, send email to
> strophe+u...@googlegroups.com
> <mailto:strophe%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/group/strophe?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Strophe" group.
> To post to this group, send email to str...@googlegroups.com
> <mailto:str...@googlegroups.com>.
> To unsubscribe from this group, send email to
> strophe+u...@googlegroups.com
> <mailto:strophe%2Bunsu...@googlegroups.com>.
Does it work if you use http://<Host>/http-bind/? Ie, still using the
full http URL?
My guess is that unless you are set up for Cross Orgin Resource
Sharing on your connection manager, this is considered a cross-domain
request and will fail.
Another workaround would be to use the strophe.flxhr.js plugin.
jack.
I think that CORS headers are your only option. You will probably want
to e-mail the Openfire guys about supporting CORS, hack it yourself
(it's just adding an extra two headers to each HTTP response, so it's
very simple), or use Punjab which can be a connection manager to any
XMPP server and does support CORS.
jack.