CORS header ‘Access-Control-Allow-Origin’ and IWS -- WEB400

Subject: CORS header ‘Access-Control-Allow-Origin’ and IWS
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Sun, 24 Feb 2019 17:06:36 -0600
List-archive: <https://archive.midrange.com/web400/>
List-help: <mailto:web400-request@lists.midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.lists.midrange.com>
List-post: <mailto:web400@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@lists.midrange.com?subject=unsubscribe>

This keeps coming back to hurt me. Is there a place in the IWS wizard process that deals with this issue? When I Google for help two things stand out:

1. There is a really lot of discussion about CORS, at all levels of
experience.
2. The examples, explanations, cautions, and instructions fly way
above the head of the average RPG programmers that I know.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CORS header ‘Access-Control-Allow-Origin’ and IWS , Danny Rodius
Re: CORS header ‘Access-Control-Allow-Origin’ and IWS , Tim Fathers

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.