Hello!

-
Hello!

I would've thought that, in the latest incarnations, Indy would automatically create the necessary components to support HTTPs.

However, I am getting a 501/Not implemented. Now, I do know that this is supposed to come from the server, BUT if I call that very URL from the browser, I get a JSON response. Well, I get a rubbish response :) but it's still JSON.

So it must be coming from Indy.

Anybody knows about this? Am I misguided?

Thanks :)

A

Comments

  1. Jeroen Wiert PluimersSeptember 22, 2016 at 4:04 AM

    did you try a full network trace (for instance WireShark) to see who is generating the 501?

    ReplyDelete
  2. David HeffernanSeptember 22, 2016 at 4:51 AM

    Yes. Yes.

    ReplyDelete
  3. Asbjørn HeidSeptember 22, 2016 at 1:21 PM

    Jeroen Wiert Pluimers Wouldn't an interceptor be enough?

    ReplyDelete
  4. David NottageSeptember 22, 2016 at 3:38 PM

    Indy does create them, if you use a URL with https in it. We (i.e. Frontier Software) do it in our mobile app. You might want to show an example.

    ReplyDelete
  5. Jeroen Wiert PluimersSeptember 22, 2016 at 4:21 PM

    Asbjørn Heid if it's Delphi both sides and you think the problem is inside Delphi then it would work. I do too much cross-tool development that WireShark is in my standard tool kit.

    ReplyDelete
  6. Asbjørn HeidSeptember 22, 2016 at 6:03 PM

    Jeroen Wiert Pluimers Huh?

    ReplyDelete
  7. Jeroen Wiert PluimersSeptember 23, 2016 at 2:04 AM

    Asbjørn Heid I was tired and sleeping while typing. Fixed the comment.

    ReplyDelete
  8. Asbjørn HeidSeptember 23, 2016 at 2:20 AM

    Jeroen Wiert Pluimers Hehe, comment 2.0 makes a lot more sense :)

    I was thinking it would help even if he's just using Indy on the client side, as he should be able to see what request Indy sends. I recently did that to debug some FTP issues when connecting to a z/OS server using Indy FTP client component.

    But yeah if you got Wireshark installed and ready for action, go for it :)

    ReplyDelete
  9. Andrea RaimondiSeptember 23, 2016 at 2:32 AM

    Turns out I'd been daft and forgot setting the ContentType and the Accepts headers. D'oh!

    ReplyDelete
  10. David HeffernanSeptember 23, 2016 at 3:05 AM

    How could anybody have helped you with that given what you presented? It would be so much to everyone's benefit (especially your own) if you spent more time thinking about how to present your problems when you ask for help.

    ReplyDelete
  11. Asbjørn HeidSeptember 23, 2016 at 3:23 AM

    Given that it worked with a regular browser, bad and/or missing headers was my first thought, and hence why I suggested the interceptor...

    ReplyDelete

Post a Comment