| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | PCP web client on different domain |
| From: | Amer Ather <aather@xxxxxxxxxxx> |
| Date: | Wed, 4 Jun 2014 17:23:46 -0700 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=HXXs3TDi5iz9eoGa31fVgX0oYrC3MY6bB0ZTw/Xdr1M=; b=qioxGL7V5aWJwN7w2wVPMsUsWNRgNIvCbyhcGtsbREGF1D/o+v1QPMddr1V86gSP9U /zcolD2HJAiLe+dgFe5x92Po3NX41A1XvVr+sAKjNbFNXgtt4imSVz2GXuyCQIP1OA1X fEhzc1W5fm+dGm1Kj0j6sh4tHuoW8t1PHTZNQ= |
|
Our client application is running on a different instance than the one serving PCP. That means for all _javascript_ API requests to PCP server we need to include an extra header in order for our browser client to accept the response:
Access-Control-Allow-Origin: * This is fairly standard on any API that is meant to be used by external clients. Do we need to enable some configure option in PCP in order to make it work? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Dave Brolley |
|---|---|
| Next by Date: | Re: [pcp] pmcc.py bug?, Mark Goodwin |
| Previous by Thread: | Re: [pcp] PCP Updates: Active Probing for __pmDiscoverServices() / pmfind, Dave Brolley |
| Next by Thread: | Re: [pcp] PCP web client on different domain, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |