[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using raw to post data



   Thanks Scott. I have a Wireshark capture. I'll examine it and probably
   ask some questions Monday. Thanks!

   On Fri, Feb 27, 2015 at 3:48 PM, Scott Klement <[1]sk@xxxxxxxxxxxxxxxx>
   wrote:

     Mike,
     Technically, a "raw" socket means he's not letting the operating
     system fill in the protocol details, but rather he's coding the
     TCP/IP protocols by hand in his program.� But, I don't think he
     meant that.� � I think he just meant that they wrote the program
     using sockets rather than getting/buying a package that does the
     work for them.
     So, it really means absolutely nothing.
     Whomever wrote the Apache web server for IBM i did so by "listening
     on a socket".� �Whomever wrote IIS for Windows did so by
     "listening on a socket".� �This piece of information means
     absolutely nothing. All TCP/IP applications of any kind are written
     using sockets.
     Most likely, it's just really fussy about what data it accepts and
     does not.� You need to figure out what it wants, and send it
     accordingly.
     -SK
     On 2/27/2015 2:05 PM, Michael Ryan wrote:

     � � Well...this may be an issue...
     � � From me to vendor:
     � � Usually when I communicate using an HTTP POST, it�s
     something like
     � � this:
     � � [2]http://www.twcs.cc/tfcapps/tfc_process_sts.tsk
     � � Where http is the protocol, [2][3]www.twcs.cc is the host URL,
     and
     � � tfcapps/tfc_process_sts.tsk is the thing that gets executed.
     � � I'm just sending this to the device:
     � � [4]http://192.168.1.99:986
     � � With no task or program to be executed. I think I need
     something there.
     � �     � � Vendor response:
     � � No, that isn't quite how we have it built. We are listening on
     the raw
     � � socket for an inbound tcp request with http headers. Not
     really a
     � � standard web service.
     � � What can I do?

   -----------------------------------------------------------------------
   This is the FTPAPI mailing list.� To unsubscribe, please go to:
   [5]http://www.scottklement.com/mailman/listinfo/ftpapi
   -----------------------------------------------------------------------

References

   1. mailto:sk@xxxxxxxxxxxxxxxx
   2. http://www.twcs.cc/tfcapps/tfc_process_sts.tsk
   3. http://www.twcs.cc/
   4. http://192.168.1.99:986/
   5. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------