Announcement

Collapse
No announcement yet.

https support for http sender

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I tried to GET https://google.com from the free version's HTTP sender, and it worked. I think it usually fails for people because they are using self-signed certs, and java can't validate the certificate.

    Comment


    • #17
      The built in HTTP sender works for me now using an Https URL. For me it was all about the inbound,outbound, and returning destination settings. I just originally thought because of the red X that it was not working/available. I have to say that the red X is a bit confusing. And having Https in the sender list might also be a good idea? What do you think?

      Comment


      • #18
        I think it would clutter the list. https is just http+ssl, so the http sender still makes sense. If they were separated, would smb writer, sftp writer, webdav writer, etc... need to be separated from the file writer too?

        Comment


        • #19
          The file Writer has a list where one can clearly select if they want sftp.
          I have never been confused on that page.

          Comment


          • #20
            I just mean that it may not be immediately intuitive that when you want to send data via a network protocol like sftp that you need to choose a file writer in the first place. Technically you are sending over tcp, and it may or may not end up actually getting written to a file on the other end.

            When you send to an https destination, you're still using http as the protocol. The two property screens would be the same. Maybe it would be better to change the red X to a yellow warning, because I do see how that part is confusing.

            Comment

            Working...
            X