[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using raw to post data
In my IBMi trace, I see this:
*E � úc@ @ � �� ��� c¢î �û¥¹ <�*
*P ÿÿ P �POST / HTTP/1.1 �Host: 1*
*[1]92.168.1.99:986 �User-Agent: htt*
*p-api/1.24 �Content-Type: text/x*
*ml �Content-Length: 122 � � � � *
and this:
*E �¤úd@ @ � �� ��� c¢î �û¦* <�*
*P ÿÿ [ � � � � � � � � � � � � �*
* � �<TRANSACTION> �<TRANSACTIONT*
*YPE>INTERACTIVECREDITAUTH</TRANS*
*ACTIONTYPE> �<CREDITAMT>1.00</CR*
*EDITAMT> �</TRANSACTION> � � � �*
Which matches (I think) what's coming from the PC. I *do* have a couple
of extra CRLF pairs before the <TRANSACTION>. I'll try again without
those.
On Tue, Mar 3, 2015 at 12:02 PM, Michael Ryan <[2]michaelrtr@xxxxxxxxx>
wrote:
I have the source for this code, so I'll have to dig through and see
what it provides.
I may be able to circle in a developer at the vendor.
I *do* have a Wireshark trace that they sent me, and one that I
generated from my PC (which was successful).
I also have an IBMi trace (done with TRCCNN) that's showing the HTTP
headers and the XML payload.
On Tue, Mar 3, 2015 at 11:52 AM, Scott Klement <[3]sk@xxxxxxxxxxxxxxxx>
wrote:
Mike,
Did they give you the values of these variables?
xmlInput = request.Text;
url.Text
httpRequest.ContentType = contentType.Text;
On 3/3/2015 10:24 AM, Michael Ryan wrote:
� � This is how it's being done in C#. Does this shed any light?
thanks!
� � �� �� �� � � private string httpPost()
� � � � � � � � �� {
� � � � � � � � � � � � �� HttpWebRequest
httpRequest;
� � � � � � � � � � � � �� HttpWebResponse
httpResponse;
� � � � � � � � � � � � �� Stream
httpPostStream;
� � � � � � � � � � � � �� BinaryReader
httpResponseStream;
� � � � � � � � � � � � �� Byte[] postBytes;
� � � � � � � � � � � � �� string xmlInput;
� � � � � � � � � � � � �� Byte[] response;
� � �
� � � � � � � � � � � � �� ServicePointManager.SecurityProtocol =
� � SecurityProtocolType.Ssl3;
� � �
� � � � � � � � � � � � �
� � � � � � � � � � � � � � xmlInput =
request.Text;//.Replace("\r",
� � "\r\n") + '\n' + '\r';
� � �
� � � � � � � � � � � � �� httpRequest =
� � (HttpWebRequest)WebRequest.CreateDefault(new Uri(url.Text));
� � � � � �
� � �
� � � � � � � � � � � � �� httpRequest.KeepAlive = persist.Checked;
� � �
� � �
� � � � � � � � � � � � �� httpRequest.Method
= "POST";
� � � � � � � � � � � � �
� � � � � � � � � � � � � �
httpRequest.Proxy.Credentials =
� � System.Net.CredentialCache.DefaultCredentials;
� � � � � � � � � � � � �� postBytes =
Encoding.UTF8.GetBytes(xmlInput);
� � �
� � � � � � � � � � � � �� httpRequest.ContentLength = postBytes.Length;
� � � � � � � � � � � � �� httpRequest.ContentType = contentType.Text;
� � �
� � � � � � � � � � � � �� httpPostStream =
httpRequest.GetRequestStream();
� � �
� � � � � � � � � � � � �� httpPostStream.Write(postBytes, 0,
� � postBytes.Length);
� � � � � � � � � � � � � �
httpPostStream.Close();
� � � � � � � � � � � � �� httpResponse =
� � (HttpWebResponse)httpRequest.GetResponse();
� � �
� � � � � � � � � � � � �� httpResponseStream
= new
� � BinaryReader(httpResponse.GetResponseStream(), Encoding.ASCII);
� � � � � � � � � � � � �� int lengthToRead =
int.Parse(packetLength.Text);
� � � � � � � � � � � � �� if (lengthToRead ==
0)
� � � � � � � � � � � � � � � � �� lengthToRead =
� � (Int32)httpResponse.ContentLength;
� � � � � � � � � � � � �� response =
� � httpResponseStream.ReadBytes(lengthToRead);
� � � � � � � � � � � � �� return
� � System.Text.Encoding.ASCII.GetString(response);
� � � � � � � � �� }
� � On Tue, Mar 3, 2015 at 10:49 AM, Charles Wilt
� � <[1][4]charles.wilt@xxxxxxxxx> wrote:
� � � �� � As Paul points out, wireshark by itself can only
capture data
� � � to/from
� � � �� � your PC.
� � � �� � You might be able to reconfigure your network
switch to
� � � duplicate other
� � � �� � traffic to your PC.
� � � �� � However, easier just to start a comm trace on
your IBM i to
� � � capture the
� � � �� � packets it is sending.
� � � �� � Charles
� � � �� � On Tue, Mar 3, 2015 at 9:26 AM, Michael Ryan
� � � <[1][2][5]michaelrtr@xxxxxxxxx>
� � � �� � wrote:
� � � �� �� � ��� � Ok...I'm using Wireshark to
capture the packets, but I
� � � seem to
� � � �� �� � be
� � � �� �� � ��� � having problems. There's a
test program that runs on
� � � my PC. I'm
� � � �� �� � able to
� � � �� �� � ��� � capture and display the
packets between my PC and the
� � � device.
� � � �� �� � That
� � � �� �� � ��� � process works, and the packets
are what I expect.�
� � � �� �� � ��� � I'm having a problem
specifying two different hosts
� � � (the IBMi
� � � �� �� � and the
� � � �� �� � ��� � device) for either capturing
just those packets
� � � (capture
� � � �� �� � filter) or
� � � �� �� � ��� � displaying just those packets
(display filter). Any
� � � ideas? What
� � � �� �� � do I
� � � �� �� � ��� � need to specify for capture
and/or display filters to
� � � see all
� � � �� �� � the
� � � �� �� � ��� � packets on the network that
are between these two IP
� � � addresses?
� � � �� �� � ��� � Thanks!
� � � �� �� � ��� � On Mon, Mar 2, 2015 at 2:14
PM, Michael Ryan
� � � �� �� � <[1][2][3][6]michaelrtr@xxxxxxxxx>
� � � �� �� � ��� � wrote:
� � � �� �� � ��� � All good thoughts Mike. I plan
on getting the traces
� � � tomorrow
� � � �� �� � with
� � � �� �� � ��� � Wireshark. I'll share what I
get in hopes you all can
� � � help!
� � � �� �� � Thanks!
� � � �� �� � ��� � On Mon, Mar 2, 2015 at 2:01
PM, Mike Krebs
� � � �� �� � ��� �
<[2][3][4][7]mkrebs@xxxxxxxxxxxxxxxxxx> wrote:
� � � �� �� � ��� ��� � Do you have the C#
code running? Or are you using
� � � it as
� � � �� �� � template to
� � � �� �� � ��� ��� � work from? If you
have working code and are not
� � � sure of the
� � � �� �� � ��� ��� � parameters, then
wireshark is probably a good
� � � idea.���� If it
� � � �� �� � is just
� � � �� �� � ��� ��� � a template, share the
C# code if you can and one
� � � of the
� � � �� �� � ��� ��� � multi-lingual
programmers will help interpret.
� � � �� �� � ��� ��� � Considering it
appears to be some sort of error
� � � with the
� � � �� �� � ��� ��� � communication, I
would go back to the "am I
� � � hitting a valid
� � � �� �� � url?"
� � � �� �� � ��� ��� � question. And that,
the wireshark will help with.
� � � You should
� � � �� �� � clearly
� � � �� �� � ��� ��� � see the POST
information being sent in the
� � � wireshark.
� � � �� �� � ��� ��� � Since appears to be a
credit/debit system, I
� � � assume the data
� � � �� �� � itself
� � � �� �� � ��� ��� � is going to be
encrypted by TLS in the wireshark.
� � � So, that
� � � �� �� � is not
� � � �� �� � ��� ��� � going to be much
help.
� � � �� �� � ��� ��� � Should your URL be
https:?
� � � �� �� � ��� ��� � -----Original
Message-----
� � � �� �� � ��� ��� � From:
� � � [3][4][5][8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� � ��� ��� �
� � � [mailto:[4][5][6][9]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx]
On
� � � �� �� � Behalf Of
� � � �� �� � ��� ��� � Michael Ryan
� � � �� �� � ��� ��� � Sent: Monday, March
2, 2015 11:07 AM
� � � �� �� � ��� ��� � To: HTTPAPI and
FTPAPI Projects
� � � �� �� � ��� ��� � Subject: Re: Using
raw to post data
� � � �� �� � ��� � Ok...I'm getting a -1 here in
recvresp:
� � � �� �� � ��� � eval���� ���� ���� wwRec = comm_lineread( peComm
� � � �� �� � ��� � ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���
� � � ���� ���� ���� ���� � :
� � � �� �� � wwPos
� � � �� �� � ��� � ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���
� � � ���� ���� ���� ���� � :
� � � �� �� � wwLeft
� � � �� �� � ��� � ���� ���� ���� ���� ���� ���� ���� ���� ���� ���� ���
� � � ���� ���� ���� ���� � :
� � � �� �� � peTimeout )
� � � �� �� � ��� � It then throws the
'recvresp(): end with err message.
� � � �� �� � ��� � Wireshark is my option?
� � � �� �� � ��� � Thanks...
� � � �� �� � ��� � On Fri, Feb 27, 2015 at 4:30
PM, Charles Wilt
� � � �� �� � ��� �
<[5][6][7][10]charles.wilt@xxxxxxxxx>
� � � �� �� � ��� � wrote:
� � � �� �� � ��� � >���� ���� The
C# code might be helpful...
� � � �� �� � ��� � >���� ���� I'd
guess if it's doing a HTTP post, you'll
� � � be able to
� � � �� �� � use HTTP
� � � �� �� � ��� � API...
� � � �� �� � ��� � >���� ���� The
wireshark capture certainly will.
� � � �� �� � ��� � >���� ���� Charles
� � � �� �� � ��� � >���� ���� On
Fri, Feb 27, 2015 at 3:37 PM, Michael
� � � Ryan
� � � �� �� � ��� �
<[1][6][7][8][11]michaelrtr@xxxxxxxxx>
� � � �� �� � ��� � >���� ���� wrote:
� � � �� �� � ��� � >
� � � �� �� � ��� � >���� ���� ���� ����� � I think you're right. I just
� � � asked them for
� � � �� �� � what is
� � � �� �� � ��� � actually
� � � �� �� � ��� � >���� ���� ���� sent and
� � � �� �� � ��� � >���� ���� ���� ����� � received by the device, and
� � � they gave me
� � � �� �� � some C# code
� � � �� �� � ��� � (with
� � � �� �� � ��� � >���� ���� ���� does do an
� � � �� �� � ��� � >���� ���� ���� ����� � HTTP POST) and the XML.
� � � �� �� � ��� � >
� � � �� �� � ��� � > References
� � � �� �� � ��� � >
� � � �� �� � ��� � >���� ���� 1.
mailto:[7][8][9][12]michaelrtr@xxxxxxxxx
� � � �� �� � ��� � >
� � � �� �� � ��� � >
� � � �� �� � �
� � � �� �� � �
� � � ------------------------------------------------------------------
� � � �� �� � ----
� � � �� �� � ��� ��� � > - This is the
FTPAPI mailing list.���� To
� � � unsubscribe,
� � � �� �� � please go to:
� � � �� �� � ��� � >
� � � [8][9][10][13]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� � ��� � >
� � � �� �� � �
� � � �� �� � �
� � � ------------------------------------------------------------------
� � � �� �� � ----
� � � �� �� � ��� � > -
� � � �� �� � ��� � >
� � � �� �� � ��� � >
� � � �� �� � �
� � � �� �� � �
� � � ------------------------------------------------------------------
� � � �� �� � -----
� � � �� �� � ��� � This is the FTPAPI mailing
list.���� To unsubscribe,
� � � please go
� � � �� �� � to:
� � � �� �� � ��� �
� � � [9][10][11][14]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� � �
� � � �� �� � �
� � � ------------------------------------------------------------------
� � � �� �� � -----
� � � �� �� � References
� � � �� �� � ��� � 1.
mailto:[11][12][15]michaelrtr@xxxxxxxxx
� � � �� �� � ��� � 2.
mailto:[12][13][16]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� �� � ��� � 3.
� � � mailto:[13][14][17]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� � ��� � 4.
� � � mailto:[14][15][18]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� � ��� � 5.
mailto:[15][16][19]charles.wilt@xxxxxxxxx
� � � �� �� � ��� � 6.
mailto:[16][17][20]michaelrtr@xxxxxxxxx
� � � �� �� � ��� � 7.
mailto:[17][18][21]michaelrtr@xxxxxxxxx
� � � �� �� � ��� � 8.
� � � [18][19][22]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� � ��� � 9.
� � � [19][20][23]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �
� � � �
------------------------------------------------------------------
� � � --
� � � �� �� � ---
� � � �� �� � This is the FTPAPI mailing list.��� To
unsubscribe, please
� � � go to:
� � � �� �� �
[20][21][24]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �
� � � �
------------------------------------------------------------------
� � � --
� � � �� �� � ---
� � � References
� � � �� � 1. mailto:[22][25]michaelrtr@xxxxxxxxx
� � � �� � 2. mailto:[23][26]michaelrtr@xxxxxxxxx
� � � �� � 3. mailto:[24][27]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� � 4.
mailto:[25][28]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 5.
mailto:[26][29]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 6. mailto:[27][30]charles.wilt@xxxxxxxxx
� � � �� � 7. mailto:[28][31]michaelrtr@xxxxxxxxx
� � � �� � 8. mailto:[29][32]michaelrtr@xxxxxxxxx
� � � �� � 9.
[30][33]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� 10.
[31][34]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� 11. mailto:[32][35]michaelrtr@xxxxxxxxx
� � � �� 12. mailto:[33][36]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� 13.
mailto:[34][37]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� 14.
mailto:[35][38]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� 15. mailto:[36][39]charles.wilt@xxxxxxxxx
� � � �� 16. mailto:[37][40]michaelrtr@xxxxxxxxx
� � � �� 17. mailto:[38][41]michaelrtr@xxxxxxxxx
� � � �� 18.
[39][42]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� 19.
[40][43]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� 20.
[41][44]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � --------------------------------------------------------------------
� � � ---
� � � This is the FTPAPI mailing list.�� To unsubscribe,
please go to:
� � � [42][45]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � --------------------------------------------------------------------
� � � ---
References
� � 1. mailto:[46]charles.wilt@xxxxxxxxx
� � 2. mailto:[47]michaelrtr@xxxxxxxxx
� � 3. mailto:[48]michaelrtr@xxxxxxxxx
� � 4. mailto:[49]mkrebs@xxxxxxxxxxxxxxxxxx
� � 5. mailto:[50]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � 6. mailto:[51]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � 7. mailto:[52]charles.wilt@xxxxxxxxx
� � 8. mailto:[53]michaelrtr@xxxxxxxxx
� � 9. mailto:[54]michaelrtr@xxxxxxxxx
� �10. [55]http://www.scottklement.com/mailman/listinfo/ftpapi
� �11. [56]http://www.scottklement.com/mailman/listinfo/ftpapi
� �12. mailto:[57]michaelrtr@xxxxxxxxx
� �13. mailto:[58]mkrebs@xxxxxxxxxxxxxxxxxx
� �14. mailto:[59]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �15. mailto:[60]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �16. mailto:[61]charles.wilt@xxxxxxxxx
� �17. mailto:[62]michaelrtr@xxxxxxxxx
� �18. mailto:[63]michaelrtr@xxxxxxxxx
� �19. [64]http://www.scottklement.com/mailman/listinfo/ftpapi
� �20. [65]http://www.scottklement.com/mailman/listinfo/ftpapi
� �21. [66]http://www.scottklement.com/mailman/listinfo/ftpapi
� �22. mailto:[67]michaelrtr@xxxxxxxxx
� �23. mailto:[68]michaelrtr@xxxxxxxxx
� �24. mailto:[69]mkrebs@xxxxxxxxxxxxxxxxxx
� �25. mailto:[70]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �26. mailto:[71]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �27. mailto:[72]charles.wilt@xxxxxxxxx
� �28. mailto:[73]michaelrtr@xxxxxxxxx
� �29. mailto:[74]michaelrtr@xxxxxxxxx
� �30. [75]http://www.scottklement.com/mailman/listinfo/ftpapi
� �31. [76]http://www.scottklement.com/mailman/listinfo/ftpapi
� �32. mailto:[77]michaelrtr@xxxxxxxxx
� �33. mailto:[78]mkrebs@xxxxxxxxxxxxxxxxxx
� �34. mailto:[79]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �35. mailto:[80]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �36. mailto:[81]charles.wilt@xxxxxxxxx
� �37. mailto:[82]michaelrtr@xxxxxxxxx
� �38. mailto:[83]michaelrtr@xxxxxxxxx
� �39. [84]http://www.scottklement.com/mailman/listinfo/ftpapi
� �40. [85]http://www.scottklement.com/mailman/listinfo/ftpapi
� �41. [86]http://www.scottklement.com/mailman/listinfo/ftpapi
� �42. [87]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[88]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
-----------------------------------------------------------------------
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[89]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. http://92.168.1.99:986/
2. mailto:michaelrtr@xxxxxxxxx
3. mailto:sk@xxxxxxxxxxxxxxxx
4. mailto:charles.wilt@xxxxxxxxx
5. mailto:michaelrtr@xxxxxxxxx
6. mailto:michaelrtr@xxxxxxxxx
7. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
10. mailto:charles.wilt@xxxxxxxxx
11. mailto:michaelrtr@xxxxxxxxx
12. mailto:michaelrtr@xxxxxxxxx
13. http://www.scottklement.com/mailman/listinfo/ftpapi
14. http://www.scottklement.com/mailman/listinfo/ftpapi
15. mailto:michaelrtr@xxxxxxxxx
16. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
17. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
18. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
19. mailto:charles.wilt@xxxxxxxxx
20. mailto:michaelrtr@xxxxxxxxx
21. mailto:michaelrtr@xxxxxxxxx
22. http://www.scottklement.com/mailman/listinfo/ftpapi
23. http://www.scottklement.com/mailman/listinfo/ftpapi
24. http://www.scottklement.com/mailman/listinfo/ftpapi
25. mailto:michaelrtr@xxxxxxxxx
26. mailto:michaelrtr@xxxxxxxxx
27. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
28. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
29. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
30. mailto:charles.wilt@xxxxxxxxx
31. mailto:michaelrtr@xxxxxxxxx
32. mailto:michaelrtr@xxxxxxxxx
33. http://www.scottklement.com/mailman/listinfo/ftpapi
34. http://www.scottklement.com/mailman/listinfo/ftpapi
35. mailto:michaelrtr@xxxxxxxxx
36. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
37. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
38. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
39. mailto:charles.wilt@xxxxxxxxx
40. mailto:michaelrtr@xxxxxxxxx
41. mailto:michaelrtr@xxxxxxxxx
42. http://www.scottklement.com/mailman/listinfo/ftpapi
43. http://www.scottklement.com/mailman/listinfo/ftpapi
44. http://www.scottklement.com/mailman/listinfo/ftpapi
45. http://www.scottklement.com/mailman/listinfo/ftpapi
46. mailto:charles.wilt@xxxxxxxxx
47. mailto:michaelrtr@xxxxxxxxx
48. mailto:michaelrtr@xxxxxxxxx
49. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
50. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
51. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
52. mailto:charles.wilt@xxxxxxxxx
53. mailto:michaelrtr@xxxxxxxxx
54. mailto:michaelrtr@xxxxxxxxx
55. http://www.scottklement.com/mailman/listinfo/ftpapi
56. http://www.scottklement.com/mailman/listinfo/ftpapi
57. mailto:michaelrtr@xxxxxxxxx
58. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
59. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
60. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
61. mailto:charles.wilt@xxxxxxxxx
62. mailto:michaelrtr@xxxxxxxxx
63. mailto:michaelrtr@xxxxxxxxx
64. http://www.scottklement.com/mailman/listinfo/ftpapi
65. http://www.scottklement.com/mailman/listinfo/ftpapi
66. http://www.scottklement.com/mailman/listinfo/ftpapi
67. mailto:michaelrtr@xxxxxxxxx
68. mailto:michaelrtr@xxxxxxxxx
69. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
70. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
71. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
72. mailto:charles.wilt@xxxxxxxxx
73. mailto:michaelrtr@xxxxxxxxx
74. mailto:michaelrtr@xxxxxxxxx
75. http://www.scottklement.com/mailman/listinfo/ftpapi
76. http://www.scottklement.com/mailman/listinfo/ftpapi
77. mailto:michaelrtr@xxxxxxxxx
78. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
79. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
80. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
81. mailto:charles.wilt@xxxxxxxxx
82. mailto:michaelrtr@xxxxxxxxx
83. mailto:michaelrtr@xxxxxxxxx
84. http://www.scottklement.com/mailman/listinfo/ftpapi
85. http://www.scottklement.com/mailman/listinfo/ftpapi
86. http://www.scottklement.com/mailman/listinfo/ftpapi
87. http://www.scottklement.com/mailman/listinfo/ftpapi
88. http://www.scottklement.com/mailman/listinfo/ftpapi
89. 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
-----------------------------------------------------------------------