Re: jQuery/Ajax cross domain issue and CORS -- 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: jQuery/Ajax cross domain issue and CORS
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Tue, 7 Feb 2017 14:52:28 -0600
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 2/7/2017 2:48 PM, Keith McCully wrote:

I have a Ajax client forwarding requests to a node.js server running
on the IBM i. However, as expected, I get the "No
Access-Control-Allow-Origin header on the requested resource" error.

This would be more appropriate in the WEB400 list (http://mlists.org/web400).

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: jQuery/Ajax cross domain issue and CORS , Keith McCully

This mailing list archive is Copyright 1997-2025 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.