[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: HTTPAPI to SSL Website
Scott:
I understand what you're saying. I guess the best way to describe what I
was hoping for was a "plain English" overview of the HTTP protocol,
maybe.
Sorta' like, to build a subfile you:
clear the subfile;
repeat (read a record from a file, write to the subfile) until the subfile or page is full;
EXFMT the control record;
repeat(READC the subfile to process changes).
Obviously, if you wanted to do something "fancy" with the subfile, you would have some
variation of this path, but basically those are the steps that you follow for every
subfile that you process.
I'll download and try out the code momentarily, and let you know what happens.
I'll only change that piece - I haven't made any other changes to the code that you had
suggested previously (removing the persistant connection stuff).
Jon Juracich, IBM Certified Specialist: RPG IV Developer
Sr. Staff Consultant, IBM Solutions Practice
Affiliated, Inc.
(614)889-6555, ext 355
www.aresgrp.com
Affiliated helps growing & Mid-Market organizations identify, evaluate, and implement solutions that use new & existing technology & resources that improve operational efficiency or increase revenue. Both make your organization more profitable and more successful.
________________________________________
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott Klement [sk@xxxxxxxxxxxxxxxx]
Sent: Thursday, June 26, 2008 3:06 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: HTTPAPI to SSL Website
Hi Jon,
> By a "cheat sheet" I meant something that might say, for example,
> to do an HTTPS transaction, you do:
>
> https_init();
> http_get;
> http_post;
> http_close;
A lot of what you do is going to depend on the application. In your
situation, you apparently need to first retrieve a web page, then post a
document... other situations don't have the same requirement. Some
folks only need to do a GET. Other folks only need a POST. It's really
hard to create a "cheat sheet" without taking a particular application
into account.
In generic terms, if I want to do an HTTPS GET, I have to do this:
http_url_get();
Not a very useful cheat sheet. But, you don't need to call https_init()
unless you want to modify the default SSL behavior. So I might say
"HTTPS GET with modified SSL behavior"
https_init()
https_url_get()
I dunno... I'm not sure it's all that helpful. What you have to do with
HTTPAPI is almost entirely based on what the server requires you to do,
and that makes it hard to come up with a cheat sheet. Or -- maybe it's
just the way my mind works that makes it hard...
> Thanks for your help on this - I really appreciate it. If you need additional
> info or whatever, just let me know.
Can you test the following version of HTTPAPI?
http://www.scottklement.com/httpapi/beta/
This is a copy where I've modified the Cookie routines to re-send the
cookie name in the same case (upper/lower) that it was received. I
don't know if that's the cause of your problem or not, but it's my best
guess at this point. Can you try the beta code and let me know if it
makes any difference?
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
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
-----------------------------------------------------------------------