Re: Percent-encoding of URLs (for calling web services via HTTPAPI) -- 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: Percent-encoding of URLs (for calling web services via HTTPAPI)
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
Date: Fri, 21 Jun 2024 21:18:51 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Use the http_urlEncode() routine in HTTPAPI.

On 6/21/24 7:33 PM, James H. H. Lampert via MIDRANGE-L wrote:

I'm working on a project that involves calling a web service (via HTTPAPI) that expects its parameters in the URL itself, with any non-ASCII characters (and any characters with special meanings in URLs) percent-encoded (on a UTF-8 basis).

Is there something already out there that would save me from having to write a UTF-8 percent-encoder myself?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Percent-encoding of URLs (for calling web services via HTTPAPI) , James Lampert

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.