Re: HTTP exceptions calling a web service -- MIDRANGE-L

× 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.

Subject: Re: HTTP exceptions calling a web service
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Tue, 02 Oct 2018 08:29:56 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On the Midrange List, in reply to my query, Jim It wrote:

I asked the same thing 3.5 months ago on CODE400 and you can see Scott's response.

Hmm. Well, given that it was definitely a transient, it sounds to me like something got garbled, and the solution is what I was planning to do anyway: improve my HTTP exception processing.

But that doesn't mean I'm not still interested in understanding the cause(s).

--
JHHL

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.