[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using raw to post data
Thanks Scott. I should be able to set up a span port tomorrow and get
the IBMi, a PC, and the device so I can trace all the traffic to and
from the device.
I know HTTPAPI gets an error at comm_read, but it certainly could be
something that happens prior to that. I do see Communication Error
flash on the device screen quickly, so I'm not invoking something
correctly.
On Tue, Mar 3, 2015 at 12:33 PM, Scott Klement <[1]sk@xxxxxxxxxxxxxxxx>
wrote:
Mike,
The wireshark trace from the PC might be useful.� (Don't need one
from the IBM i, the HTTPAPI debug file should have everything
needed, there.)
-SK
On 3/3/2015 11:02 AM, Michael Ryan 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
<[1][2]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][2][3]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][3][4]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][4][5]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][5][6]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][6][7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� ��� � ���� ���� �
� � � �� �� �� [mailto:[4][5][6][7][8]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][8][9]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][9][10]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][10][11]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �� ��� ��� � �
� � � �� �� �� ��� ��� � �
� � � �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� ��� ��� � ----
� � � �� �� �� ��� ��� � ���� ���� � > - This is the
� � � FTPAPI mailing list.����� To
� � � �� �� �� unsubscribe,
� � � �� �� �� ��� ��� � please go to:
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �
� � � [8][9][10][11][12]http://www.scottklement.com/mailman/listinfo/ftpap
i
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �� ��� ��� � �
� � � �� �� �� ��� ��� � �
� � � �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� ��� ��� � ----
� � � �� �� �� ��� ��� � ���� � > -
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �� ��� ��� � ���� � >
� � � �� �� �� ��� ��� � �
� � � �� �� �� ��� ��� � �
� � � �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� ��� ��� � -----
� � � �� �� �� ��� ��� � ���� �
This is the FTPAPI mailing
� � � list.����� To unsubscribe,
� � � �� �� �� please go
� � � �� �� �� ��� ��� � to:
� � � �� �� �� ��� ��� � ���� �
� � � �� �� �
� � � [9][10][11][12][13]http://www.scottklement.com/mailman/listinfo/ftpa
pi
� � � �� �� �� ��� ��� � �
� � � �� �� �� ��� ��� � �
� � � �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� ��� ��� � -----
� � � �� �� �� ��� ��� � References
� � � �� �� �� ��� ��� � ���� � 1.
� � � mailto:[11][12][13][14]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 2.
� � � mailto:[12][13][14][15]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 3.
� � � �� �� �� mailto:[13][14][15][16]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 4.
� � � �� �� �� mailto:[14][15][16][17]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 5.
� � � mailto:[15][16][17][18]charles.wilt@xxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 6.
� � � mailto:[16][17][18][19]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 7.
� � � mailto:[17][18][19][20]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� ��� � ���� � 8.
� � � �� �� �
� � � [18][19][20][21]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� ��� � ���� � 9.
� � � �� �� �
� � � [19][20][21][22]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� �
� � � �� �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� --
� � � �� �� �� ��� ��� � ---
� � � �� �� �� ��� ��� � This is the FTPAPI
mailing list.���� To
� � � unsubscribe, please
� � � �� �� �� go to:
� � � �� �� �� ��� ��� �
� � � [20][21][22][23]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� �
� � � �� �� �� �
� � � ------------------------------------------------------------------
� � � �� �� �� --
� � � �� �� �� ��� ��� � ---
� � � �� �� �� References
� � � �� �� �� ��� � 1.
mailto:[22][23][24]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� � 2.
mailto:[23][24][25]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� � 3.
mailto:[24][25][26]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� � 4.
� � � mailto:[25][26][27]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� � 5.
� � � mailto:[26][27][28]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� � 6.
mailto:[27][28][29]charles.wilt@xxxxxxxxx
� � � �� �� �� ��� � 7.
mailto:[28][29][30]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� � 8.
mailto:[29][30][31]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� � 9.
� � � [30][31][32]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� 10.
� � � [31][32][33]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� 11.
mailto:[32][33][34]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� 12.
mailto:[33][34][35]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� 13.
� � � mailto:[34][35][36]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� 14.
� � � mailto:[35][36][37]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� �� ��� 15.
mailto:[36][37][38]charles.wilt@xxxxxxxxx
� � � �� �� �� ��� 16.
mailto:[37][38][39]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� 17.
mailto:[38][39][40]michaelrtr@xxxxxxxxx
� � � �� �� �� ��� 18.
� � � [39][40][41]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� 19.
� � � [40][41][42]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �� ��� 20.
� � � [41][42][43]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �
� � � --------------------------------------------------------------------
� � � �� �� �� ---
� � � �� �� �� This is the FTPAPI mailing list.��� To unsubscribe,
� � � please go to:
� � � �� �� �� [42][43][44]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� �� �
� � � --------------------------------------------------------------------
� � � �� �� �� ---
� � � References
� � � �� �� 1. mailto:[44][45]charles.wilt@xxxxxxxxx
� � � �� �� 2. mailto:[45][46]michaelrtr@xxxxxxxxx
� � � �� �� 3. mailto:[46][47]michaelrtr@xxxxxxxxx
� � � �� �� 4. mailto:[47][48]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� �� 5.
mailto:[48][49]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� 6.
mailto:[49][50]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� �� 7. mailto:[50][51]charles.wilt@xxxxxxxxx
� � � �� �� 8. mailto:[51][52]michaelrtr@xxxxxxxxx
� � � �� �� 9. mailto:[52][53]michaelrtr@xxxxxxxxx
� � � �� � 10.
[53][54]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 11.
[54][55]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 12. mailto:[55][56]michaelrtr@xxxxxxxxx
� � � �� � 13. mailto:[56][57]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� � 14.
mailto:[57][58]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 15.
mailto:[58][59]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 16. mailto:[59][60]charles.wilt@xxxxxxxxx
� � � �� � 17. mailto:[60][61]michaelrtr@xxxxxxxxx
� � � �� � 18. mailto:[61][62]michaelrtr@xxxxxxxxx
� � � �� � 19.
[62][63]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 20.
[63][64]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 21.
[64][65]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 22. mailto:[65][66]michaelrtr@xxxxxxxxx
� � � �� � 23. mailto:[66][67]michaelrtr@xxxxxxxxx
� � � �� � 24. mailto:[67][68]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� � 25.
mailto:[68][69]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 26.
mailto:[69][70]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 27. mailto:[70][71]charles.wilt@xxxxxxxxx
� � � �� � 28. mailto:[71][72]michaelrtr@xxxxxxxxx
� � � �� � 29. mailto:[72][73]michaelrtr@xxxxxxxxx
� � � �� � 30.
[73][74]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 31.
[74][75]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 32. mailto:[75][76]michaelrtr@xxxxxxxxx
� � � �� � 33. mailto:[76][77]mkrebs@xxxxxxxxxxxxxxxxxx
� � � �� � 34.
mailto:[77][78]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 35.
mailto:[78][79]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � � �� � 36. mailto:[79][80]charles.wilt@xxxxxxxxx
� � � �� � 37. mailto:[80][81]michaelrtr@xxxxxxxxx
� � � �� � 38. mailto:[81][82]michaelrtr@xxxxxxxxx
� � � �� � 39.
[82][83]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 40.
[83][84]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 41.
[84][85]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � �� � 42.
[85][86]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � --------------------------------------------------------------------
� � � ---
� � � This is the FTPAPI mailing list.�� To unsubscribe,
please go to:
� � � [86][87]http://www.scottklement.com/mailman/listinfo/ftpapi
� � � --------------------------------------------------------------------
� � � ---
� � --------------------------------------------------------------------
---
� � This is the FTPAPI mailing list.�� To unsubscribe, please
go to:
� � [87][88]http://www.scottklement.com/mailman/listinfo/ftpapi
� � --------------------------------------------------------------------
---
References
� � 1. mailto:[89]sk@xxxxxxxxxxxxxxxx
� � 2. mailto:[90]charles.wilt@xxxxxxxxx
� � 3. mailto:[91]michaelrtr@xxxxxxxxx
� � 4. mailto:[92]michaelrtr@xxxxxxxxx
� � 5. mailto:[93]mkrebs@xxxxxxxxxxxxxxxxxx
� � 6. mailto:[94]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � 7. mailto:[95]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� � 8. mailto:[96]charles.wilt@xxxxxxxxx
� � 9. mailto:[97]michaelrtr@xxxxxxxxx
� �10. mailto:[98]michaelrtr@xxxxxxxxx
� �11. [99]http://www.scottklement.com/mailman/listinfo/ftpapi
� �12. [100]http://www.scottklement.com/mailman/listinfo/ftpapi
� �13. mailto:[101]michaelrtr@xxxxxxxxx
� �14. mailto:[102]mkrebs@xxxxxxxxxxxxxxxxxx
� �15. mailto:[103]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �16. mailto:[104]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �17. mailto:[105]charles.wilt@xxxxxxxxx
� �18. mailto:[106]michaelrtr@xxxxxxxxx
� �19. mailto:[107]michaelrtr@xxxxxxxxx
� �20. [108]http://www.scottklement.com/mailman/listinfo/ftpapi
� �21. [109]http://www.scottklement.com/mailman/listinfo/ftpapi
� �22. [110]http://www.scottklement.com/mailman/listinfo/ftpapi
� �23. mailto:[111]michaelrtr@xxxxxxxxx
� �24. mailto:[112]michaelrtr@xxxxxxxxx
� �25. mailto:[113]mkrebs@xxxxxxxxxxxxxxxxxx
� �26. mailto:[114]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �27. mailto:[115]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �28. mailto:[116]charles.wilt@xxxxxxxxx
� �29. mailto:[117]michaelrtr@xxxxxxxxx
� �30. mailto:[118]michaelrtr@xxxxxxxxx
� �31. [119]http://www.scottklement.com/mailman/listinfo/ftpapi
� �32. [120]http://www.scottklement.com/mailman/listinfo/ftpapi
� �33. mailto:[121]michaelrtr@xxxxxxxxx
� �34. mailto:[122]mkrebs@xxxxxxxxxxxxxxxxxx
� �35. mailto:[123]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �36. mailto:[124]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �37. mailto:[125]charles.wilt@xxxxxxxxx
� �38. mailto:[126]michaelrtr@xxxxxxxxx
� �39. mailto:[127]michaelrtr@xxxxxxxxx
� �40. [128]http://www.scottklement.com/mailman/listinfo/ftpapi
� �41. [129]http://www.scottklement.com/mailman/listinfo/ftpapi
� �42. [130]http://www.scottklement.com/mailman/listinfo/ftpapi
� �43. [131]http://www.scottklement.com/mailman/listinfo/ftpapi
� �44. mailto:[132]charles.wilt@xxxxxxxxx
� �45. mailto:[133]michaelrtr@xxxxxxxxx
� �46. mailto:[134]michaelrtr@xxxxxxxxx
� �47. mailto:[135]mkrebs@xxxxxxxxxxxxxxxxxx
� �48. mailto:[136]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �49. mailto:[137]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �50. mailto:[138]charles.wilt@xxxxxxxxx
� �51. mailto:[139]michaelrtr@xxxxxxxxx
� �52. mailto:[140]michaelrtr@xxxxxxxxx
� �53. [141]http://www.scottklement.com/mailman/listinfo/ftpapi
� �54. [142]http://www.scottklement.com/mailman/listinfo/ftpapi
� �55. mailto:[143]michaelrtr@xxxxxxxxx
� �56. mailto:[144]mkrebs@xxxxxxxxxxxxxxxxxx
� �57. mailto:[145]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �58. mailto:[146]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �59. mailto:[147]charles.wilt@xxxxxxxxx
� �60. mailto:[148]michaelrtr@xxxxxxxxx
� �61. mailto:[149]michaelrtr@xxxxxxxxx
� �62. [150]http://www.scottklement.com/mailman/listinfo/ftpapi
� �63. [151]http://www.scottklement.com/mailman/listinfo/ftpapi
� �64. [152]http://www.scottklement.com/mailman/listinfo/ftpapi
� �65. mailto:[153]michaelrtr@xxxxxxxxx
� �66. mailto:[154]michaelrtr@xxxxxxxxx
� �67. mailto:[155]mkrebs@xxxxxxxxxxxxxxxxxx
� �68. mailto:[156]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �69. mailto:[157]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �70. mailto:[158]charles.wilt@xxxxxxxxx
� �71. mailto:[159]michaelrtr@xxxxxxxxx
� �72. mailto:[160]michaelrtr@xxxxxxxxx
� �73. [161]http://www.scottklement.com/mailman/listinfo/ftpapi
� �74. [162]http://www.scottklement.com/mailman/listinfo/ftpapi
� �75. mailto:[163]michaelrtr@xxxxxxxxx
� �76. mailto:[164]mkrebs@xxxxxxxxxxxxxxxxxx
� �77. mailto:[165]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �78. mailto:[166]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
� �79. mailto:[167]charles.wilt@xxxxxxxxx
� �80. mailto:[168]michaelrtr@xxxxxxxxx
� �81. mailto:[169]michaelrtr@xxxxxxxxx
� �82. [170]http://www.scottklement.com/mailman/listinfo/ftpapi
� �83. [171]http://www.scottklement.com/mailman/listinfo/ftpapi
� �84. [172]http://www.scottklement.com/mailman/listinfo/ftpapi
� �85. [173]http://www.scottklement.com/mailman/listinfo/ftpapi
� �86. [174]http://www.scottklement.com/mailman/listinfo/ftpapi
� �87. [175]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[176]http://www.scottklement.com/mailman/listinfo/ftpapi
--------------------------------------------------------------------
---
-----------------------------------------------------------------------
This is the FTPAPI mailing list.� To unsubscribe, please go to:
[177]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. mailto:sk@xxxxxxxxxxxxxxxx
2. mailto:sk@xxxxxxxxxxxxxxxx
3. mailto:charles.wilt@xxxxxxxxx
4. mailto:michaelrtr@xxxxxxxxx
5. mailto:michaelrtr@xxxxxxxxx
6. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:charles.wilt@xxxxxxxxx
10. mailto:michaelrtr@xxxxxxxxx
11. mailto:michaelrtr@xxxxxxxxx
12. http://www.scottklement.com/mailman/listinfo/ftpapi
13. http://www.scottklement.com/mailman/listinfo/ftpapi
14. mailto:michaelrtr@xxxxxxxxx
15. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
16. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
17. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
18. mailto:charles.wilt@xxxxxxxxx
19. mailto:michaelrtr@xxxxxxxxx
20. mailto:michaelrtr@xxxxxxxxx
21. http://www.scottklement.com/mailman/listinfo/ftpapi
22. http://www.scottklement.com/mailman/listinfo/ftpapi
23. http://www.scottklement.com/mailman/listinfo/ftpapi
24. mailto:michaelrtr@xxxxxxxxx
25. mailto:michaelrtr@xxxxxxxxx
26. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
27. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
28. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
29. mailto:charles.wilt@xxxxxxxxx
30. mailto:michaelrtr@xxxxxxxxx
31. mailto:michaelrtr@xxxxxxxxx
32. http://www.scottklement.com/mailman/listinfo/ftpapi
33. http://www.scottklement.com/mailman/listinfo/ftpapi
34. mailto:michaelrtr@xxxxxxxxx
35. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
36. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
37. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
38. mailto:charles.wilt@xxxxxxxxx
39. mailto:michaelrtr@xxxxxxxxx
40. mailto:michaelrtr@xxxxxxxxx
41. http://www.scottklement.com/mailman/listinfo/ftpapi
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. mailto:charles.wilt@xxxxxxxxx
46. mailto:michaelrtr@xxxxxxxxx
47. mailto:michaelrtr@xxxxxxxxx
48. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
49. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
50. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
51. mailto:charles.wilt@xxxxxxxxx
52. mailto:michaelrtr@xxxxxxxxx
53. mailto:michaelrtr@xxxxxxxxx
54. http://www.scottklement.com/mailman/listinfo/ftpapi
55. http://www.scottklement.com/mailman/listinfo/ftpapi
56. mailto:michaelrtr@xxxxxxxxx
57. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
58. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
59. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
60. mailto:charles.wilt@xxxxxxxxx
61. mailto:michaelrtr@xxxxxxxxx
62. mailto:michaelrtr@xxxxxxxxx
63. http://www.scottklement.com/mailman/listinfo/ftpapi
64. http://www.scottklement.com/mailman/listinfo/ftpapi
65. http://www.scottklement.com/mailman/listinfo/ftpapi
66. mailto:michaelrtr@xxxxxxxxx
67. mailto:michaelrtr@xxxxxxxxx
68. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
69. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
70. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
71. mailto:charles.wilt@xxxxxxxxx
72. mailto:michaelrtr@xxxxxxxxx
73. mailto:michaelrtr@xxxxxxxxx
74. http://www.scottklement.com/mailman/listinfo/ftpapi
75. http://www.scottklement.com/mailman/listinfo/ftpapi
76. mailto:michaelrtr@xxxxxxxxx
77. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
78. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
79. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
80. mailto:charles.wilt@xxxxxxxxx
81. mailto:michaelrtr@xxxxxxxxx
82. mailto:michaelrtr@xxxxxxxxx
83. http://www.scottklement.com/mailman/listinfo/ftpapi
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. mailto:sk@xxxxxxxxxxxxxxxx
90. mailto:charles.wilt@xxxxxxxxx
91. mailto:michaelrtr@xxxxxxxxx
92. mailto:michaelrtr@xxxxxxxxx
93. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
94. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
95. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
96. mailto:charles.wilt@xxxxxxxxx
97. mailto:michaelrtr@xxxxxxxxx
98. mailto:michaelrtr@xxxxxxxxx
99. http://www.scottklement.com/mailman/listinfo/ftpapi
100. http://www.scottklement.com/mailman/listinfo/ftpapi
101. mailto:michaelrtr@xxxxxxxxx
102. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
103. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
104. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
105. mailto:charles.wilt@xxxxxxxxx
106. mailto:michaelrtr@xxxxxxxxx
107. mailto:michaelrtr@xxxxxxxxx
108. http://www.scottklement.com/mailman/listinfo/ftpapi
109. http://www.scottklement.com/mailman/listinfo/ftpapi
110. http://www.scottklement.com/mailman/listinfo/ftpapi
111. mailto:michaelrtr@xxxxxxxxx
112. mailto:michaelrtr@xxxxxxxxx
113. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
114. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
115. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
116. mailto:charles.wilt@xxxxxxxxx
117. mailto:michaelrtr@xxxxxxxxx
118. mailto:michaelrtr@xxxxxxxxx
119. http://www.scottklement.com/mailman/listinfo/ftpapi
120. http://www.scottklement.com/mailman/listinfo/ftpapi
121. mailto:michaelrtr@xxxxxxxxx
122. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
123. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
124. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
125. mailto:charles.wilt@xxxxxxxxx
126. mailto:michaelrtr@xxxxxxxxx
127. mailto:michaelrtr@xxxxxxxxx
128. http://www.scottklement.com/mailman/listinfo/ftpapi
129. http://www.scottklement.com/mailman/listinfo/ftpapi
130. http://www.scottklement.com/mailman/listinfo/ftpapi
131. http://www.scottklement.com/mailman/listinfo/ftpapi
132. mailto:charles.wilt@xxxxxxxxx
133. mailto:michaelrtr@xxxxxxxxx
134. mailto:michaelrtr@xxxxxxxxx
135. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
136. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
137. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
138. mailto:charles.wilt@xxxxxxxxx
139. mailto:michaelrtr@xxxxxxxxx
140. mailto:michaelrtr@xxxxxxxxx
141. http://www.scottklement.com/mailman/listinfo/ftpapi
142. http://www.scottklement.com/mailman/listinfo/ftpapi
143. mailto:michaelrtr@xxxxxxxxx
144. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
145. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
146. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
147. mailto:charles.wilt@xxxxxxxxx
148. mailto:michaelrtr@xxxxxxxxx
149. mailto:michaelrtr@xxxxxxxxx
150. http://www.scottklement.com/mailman/listinfo/ftpapi
151. http://www.scottklement.com/mailman/listinfo/ftpapi
152. http://www.scottklement.com/mailman/listinfo/ftpapi
153. mailto:michaelrtr@xxxxxxxxx
154. mailto:michaelrtr@xxxxxxxxx
155. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
156. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
157. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
158. mailto:charles.wilt@xxxxxxxxx
159. mailto:michaelrtr@xxxxxxxxx
160. mailto:michaelrtr@xxxxxxxxx
161. http://www.scottklement.com/mailman/listinfo/ftpapi
162. http://www.scottklement.com/mailman/listinfo/ftpapi
163. mailto:michaelrtr@xxxxxxxxx
164. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
165. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
166. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
167. mailto:charles.wilt@xxxxxxxxx
168. mailto:michaelrtr@xxxxxxxxx
169. mailto:michaelrtr@xxxxxxxxx
170. http://www.scottklement.com/mailman/listinfo/ftpapi
171. http://www.scottklement.com/mailman/listinfo/ftpapi
172. http://www.scottklement.com/mailman/listinfo/ftpapi
173. http://www.scottklement.com/mailman/listinfo/ftpapi
174. http://www.scottklement.com/mailman/listinfo/ftpapi
175. http://www.scottklement.com/mailman/listinfo/ftpapi
176. http://www.scottklement.com/mailman/listinfo/ftpapi
177. 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
-----------------------------------------------------------------------