If there was some list of error messages that you were getting, we might
be able to assist. As it is, though, "cryptic error messages" are the
only things that allow us to diagnose a problem and assist you in
resolving it.
One error message might be because you don't have a trusted third party
signing your SSL certificate.
Another might be because your ssl documentroot doesn't match your non-ssl
documentroot.
Is it an Apache error that's returned? What do your error logs say? Is
there a valid attempt to reach the data, or is the connection aborted
before the data's requested by the proxy?
These are all questions that we need to know the answers to in order to
help you isolate the problem -- and as we all know, isolating the problem
makes it possible to resolve.
---
Mat Butler, Winged Wolf <[EMAIL PROTECTED]>
SPASTIC Web Engineer SPASTIC Server Administrator
----Begin FurryCode v1.3----
FCWw5amrsw A- C+ D H+++ M+++++[servercoder] P+ R++ T+++ W Z++ Sm++
RLCT/M*/LW* a cl/u/v++++>+++++ !d e- f>++++ h++ iwf+++ j p->+ sm++
----End FurryCode v1.3----
On Wed, 19 Jul 2000, Bruno Melloni wrote:
> It was my understanding that the WAP forum (as well as all of the WAP gateway
> vendors) claim that even though you need extra components for a mobile device to
> encrypt the communication between the device and the WAP gateway, the
> communication between the WAP gateway and the web server is supposed to use SSL
> and more specifically https.
>
> Are you saying that is not so? Or are you saying that you don't know the answer
> and that the people at the WAP forum might know why the gateway to Apache/modssl
> might not be working when using https?
>
> In the meantime I'll check again with the WAP forum.
>
> bruno
>
> Bal�zs Nagy wrote:
>
> > Bruno Melloni wrote:
> > >
> > > I am absolutely new to modssl, so I apologize if this is a stupid
> > > question. I successfully built and installed Apache with modssl. I can
> > > access the home page from a web browser via http://server.domain.com and
> > > via https://server.domain.com.
> > >
> > > But I what I really want to do is serve .wml pages to WAP devices and
> > > emulators. I have no problem when I try to access
> > > http://server.domain.com/hello.wml, but I keep getting cryptic server
> > > messages when I use an https://server.domain.com/hello.wml URL. I have
> > > tried using different gateways and different mobile devices as well as
> > > emulators with no luck.
> > >
> > > Does anyone know what I might be doing wrong? And please feel free to
> > > refer me to any documentation that might explain this in detail.
> >
> > WAP does not support HTTPS. There are several standards in the works to enable
> > secure comunnications with a mobil device. This is out of topic for this list.
> > For more info, go to WAPforum.org
> >
> > Cheers,
> > bn
> > ______________________________________________________________________
> > Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> > User Support Mailing List [EMAIL PROTECTED]
> > Automated List Manager [EMAIL PROTECTED]
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
