Re: CORS header 'Access-Control-Allow-Origin'

[Scott Klement <web400@xxxxxxxxxxxxxxxx>]

Booth,

Are you confusing Web Services (APIs) with Web Pages?  These are two 
completely different things. I don't understand what home pages have to 
do with web services. If you have some reason why they'll need to work 
together in your scenario, please explain it.

This most recently e-mail seems to be complaining about port 80 and jam 
packing things onto a single server. I don't understand what that has to 
do with your original question.  Did someone tell you you had to jam 
pack things?

Then you start talking about the Internet and not i-related.  And your 
personal web site.  Are you changing the subject?  If not, I'm just not 
following the connection.

-SK


On 4/7/19 1:42 AM, Booth Martin wrote:
> This is only the first part of my confusion.  At the end of the quest 
> I want to provide Web Services as JSON data, consumable by staff 
> inside the VPN but who no need nor interest in having an i account and 
> password. They do, however need to have a place and way to consume 
> that data.
>
> I see that as being web-delivered.   Having  everything jammed and 
> packed on to one server strikes me as inviting needless conflict and 
> frustration.  Its pretty clear that not everyone gets port 80 for 
> "their" baby.  Therefore, to field an end to end solution I am going 
> to have to understand how to make it all work on the i.
>
> Is this issue really about the Internet and not i-related at all? 
> Maybe. But I am thinking there is more to it.  I've had my own web 
> site for 20+ years and generally work through these issues fairly easily.
>
>
> On 4/6/2019 9:56 PM, Scott Klement wrote:
> > Booth,
> >
> > You say you want labs/alice, labs/bob and labs/chuck to point to home 
> > pages.  Great!
> >
> > What does this have to do with ACAO, Web Services and reverse 
> > proxies?  I don't understand the connection.
> >
> > -SK