Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #18392 > unrolled thread
| Started by | "J.O. Aho" <user@example.net> |
|---|---|
| First post | 2020-10-18 16:14 +0200 |
| Last post | 2020-10-18 16:14 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.php
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Chrome and passing on cross-origin "J.O. Aho" <user@example.net> - 2020-10-18 16:14 +0200
| From | "J.O. Aho" <user@example.net> |
|---|---|
| Date | 2020-10-18 16:14 +0200 |
| Subject | Re: Chrome and passing on cross-origin |
| Message-ID | <hv30taFsp2hU1@mid.individual.net> |
On 18/10/2020 14.37, The Doctor wrote: > In Firefox, Waterfox, SeaMonkey, Opera and other similar browsers > > if the nginx.conf lines I comment above are turn off, the page > fails like it does in Chrome, but when I turn comment the > mention configuration line, Firefox et al works, and Mozilla observer > is not happy. > > I need to get this solved like yesterday! This is unrelated to PHP, this is about crossdomain javascript. Nowadays you should tell which domains are ok to include 3rd party javascript, the more specific you can be the better. You should avoid of including 3rd party scripts, have a local copy which you have verified with checksums that it's thew correct script and serve it from your domain. Don't forget to keep it updated so you won't have a bad vulnerability that someone can take advantage of. -- //Aho
Back to top | Article view | comp.lang.php
csiph-web