× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Those appear to be Apache server directives, Paul. I believe the OP was
referring to the client side (ie, HTTPAPI).

Bradley V. Stone
www.bvstools.com
GreenTools for PayPal <https://www.bvstools.com/g4pp.html>: Easily send
PayPal invoices from your IBM i applications using RPG ILE! Process
refunds, get account balances and more!

On Mon, Oct 8, 2018 at 4:16 PM Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

We have a similar setup, and also changed to using a persistent
connection, for both eliminating timeouts and performance issues.
Below were the HTTP directives that were needed for persistent connection.

KeepAliveTimeout 86400
MaxKeepAliveRequests 0

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
James H. H. Lampert
Sent: Friday, October 05, 2018 8:40 PM
To: Midrange Systems Technical Discussion; HTTPAPI and FTPAPI Projects
Subject: Something I don't quite understand, involving HTTPAPI calls
(cross-posted to the Midrange and HTTPAPI Lists)

Ladies and Gentlemen:

I don't quite get this:
In order to do a PUT, I have to do a "http_persist_open" and a
"http_persist_close." And when I use the higher-level calls to do GET
and POST operations, they call those lower-level routines.

And some recent threads on the RPG List tell me that we can stick a
whole series of requests between the "http_persist_open" and the
"http_persist_close."

But everything I've ever read or heard about HTTP tells me that HTTP
doesn't use persistent connections. That "persist" and "HTTP" don't even
belong in the same sentence.

Can somebody explain this seeming oxymoron?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.