On Wed, Aug 06, 2014 at 09:44:40PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.
Actually, that was the issue. You're right, there's no need to use SSL
with localhost. We
On Mon, Aug 04, 2014 at 08:29:02PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
443 is listening on localhost. As you suggested, we tried curl from
the localhost with both the FQDN and localhost URLs. We had limited
success (without any message content), but it still fails with rt-
If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.
Actually, that was the issue. You're right, there's no need to use SSL with
localhost. We have a rewrite from 80 to 443 for all interfaces and it always
forces us to use https. I
On Thu, Jul 31, 2014 at 09:03:16PM +, Richards, Matthew E ERDC-RDE-CERL-IL
wrote:
I increased the timeout from 180 to 750 added extra debugging to the code to
get more information. I replaced our URL with localhost for security:
Are you actually listening with SSL on localhost? Is your
Hi Kevin,
Thank you for the reply.
Are you actually listening with SSL on localhost? Is your webserver
configured to listen and allow that through to RT?
443 is listening on localhost. As you suggested, we tried curl from the
localhost with both the FQDN and localhost URLs. We had
