Re: Chrome and passing on cross-origin

From	"J.O. Aho" <user@example.net>
Newsgroups	comp.lang.javascript, comp.lang.php, comp.infosystems.www.authoring.html, comp.infosystems.www.authoring.misc
Subject	Re: Chrome and passing on cross-origin
Followup-To	comp.lang.javascript
Date	2020-10-18 16:14 +0200
Message-ID	<hv30taFsp2hU1@mid.individual.net> (permalink)
References	<rmdmmp$2c5l$3@gallifrey.nk.ca> <rmerb4$30qm$6@gallifrey.nk.ca> <rmfr3v$1nn4$49@gallifrey.nk.ca> <2924c70d-67bd-468a-a480-bd1741bb1158n@googlegroups.com> <rmhctg$qg5$5@gallifrey.nk.ca>

Cross-posted to 4 groups.

Followups directed to: comp.lang.javascript

Show all headers | View raw

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 comp.lang.php | Previous | Next | Find similar | Unroll thread

Thread

Re: Chrome and passing on cross-origin "J.O. Aho" <user@example.net> - 2020-10-18 16:14 +0200

csiph-web