|
I am finding that I need to write my own sub procedures to do the socket writes because they are conflicting with what I want to send. I think that may be my problem. . . Now that I know I should be able do multiple writes I will go forward with that. One other question. What are the benefits to using send() and recv() vs. read() and write() to do my socket processing? In Scott Klements tutorial he uses send() and recv() and in the GETURI tool Brad Stone uses read() and write(). Just wondering. Aaron Bartell -----Original Message----- From: Brad Stone [mailto:brad@bvstools.com] Sent: Wednesday, October 16, 2002 8:30 AM To: web400@midrange.com Subject: Re: [WEB400] HTTP Headers Should work. Did it? On Tue, 15 Oct 2002 22:54:18 -0500 "Bartell, Aaron L. (TC)" <ALBartell@taylorcorp.com> wrote: > New problem. > > In my quest to make this email utility as dynamic as > possible I am not > limiting myself to the 32767 characters a variable can > hold, but instead am > writing the body of the email to an ASCII text file and > then reading it in > 1024 bytes at a time and shoving that at the socket > connection. Here's my > question. . . can I keep pumping data into the connection > and just send two > CRLF's at the very end to indicate that I am done? So it > would look like > this (psuedo code) > > wrtLine('...') > wrtLine('...') > wrtLine('...') > wrtLine('...') > wrtLine(CRLF) > read() > > Thanks in advance, > Aaron Bartell > > > -----Original Message----- > From: Bartell, Aaron L. (TC) > [mailto:ALBartell@taylorcorp.com] > Sent: Tuesday, October 15, 2002 9:36 PM > To: 'web400@midrange.com' > Subject: RE: [WEB400] HTTP Headers > > > I got it working. It was related to how I was reading > the socket back in. > Instead of using recv() I did a read() and that seemed to > do the trick. Not > sure why it would have been puking on me. . . > > Hmmm... that one took me a couple of days, ouch :-| > > Aaron Bartell > > -----Original Message----- > From: Bartell, Aaron L. (TC) > [mailto:ALBartell@taylorcorp.com] > Sent: Tuesday, October 15, 2002 7:13 PM > To: 'web400@midrange.com' > Subject: RE: [WEB400] HTTP Headers > > > >It looks like you have 2 newlines after HTTP/1.1 (I see > two boxes on my > display). > > D crlf C CONST(X'0D25') > > I am concatenating crlf onto the end of the http version. > This should leave > two spaces correct? being that 0D is one character and 25 > is another. It > shouldn't be showing up as one combined character. . . > right? > > Aaron > > -----Original Message----- > From: Brad Stone [mailto:brad@bvstools.com] > Sent: Tuesday, October 15, 2002 6:29 PM > To: web400@midrange.com > Subject: Re: [WEB400] HTTP Headers > > > Aaron, > > > Right now my header looks like this(I took out my real > IP > > address): > > > > GET http://99.99.99.99:8080/taylor/EmailServlet?xml=<Email> > > <Subject>This%20is%20the%20subject.</Subject><ToAddress><Int > > ernetAddress>albartell@mycompany.com</InternetAddress><Name > > >Aaron%20Bartell</Name></ToAddress><FromAddress><InternetAdd > > ress>albartell@mycompany.com</InternetAddress><Name>Aaron%2 > > 0Bartell</Name></FromAddress><Body>Hi%20there</Body><URLAtta > > chment><Location>http://hotmail.com</Location><Name>hotmail. > > html</Name></URLAttachment></Email> HTTP/1.1 Host: > > 99.99.99 > > .99:8080 > > It looks like you have 2 newlines after HTTP/1.1 (I see > two > boxes on my display). This could cause a problem as it > will > ignore or misinterprert the Host: portion of the header. > Remember, 2 newlines means "I'm done!" So make sure you > don't have 2 somewhere. > > The reason I think there are 2 after HTTP/1.1 is because > if > there are 2 after the Host parm, where I also see two > boxes, > I would assume there are 2 in the prior position as well > causing an abnormal end in your case. And if I recall > from > a previous inquiry, you needed the Host HTTP header for > it > to work. > > Brad > www.bvstools.com > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) > mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/web400. > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) > mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/web400. > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) > mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/web400. > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) > mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/web400. > Bradley V. Stone BVS.Tools www.bvstools.com _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/web400 or email: WEB400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
