IRC logs for #aegir, 2019-11-15 (GMT)

2019-11-14
2019-11-16
TimeNickMessage
[11:12:20]* mutin-sa has quit (Read error: Connection reset by peer)
[11:12:49]* mutin-sa has joined #aegir
[12:11:52]* xurizaemon has quit (Ping timeout: 252 seconds)
[12:13:08]* xurizaemon has joined #aegir
[23:25:32]* shaneonabike has joined #aegir
[01:26:20]* gandhiano[m] has joined #aegir
[02:03:31]* ergonlogic[m] has joined #aegir
[02:03:31]* helmo42[m] has joined #aegir
[02:03:31]* GitterIntegratio has joined #aegir
[02:03:31]* Github[m]1 has joined #aegir
[02:18:16]* colan[m] has joined #aegir
[02:18:16]* jonpugh[m] has joined #aegir
[02:18:17]* sensespidey[m] has joined #aegir
[02:18:17]* ricardoamaro_ has joined #aegir
[02:18:17]* betz[m]2 has joined #aegir
[02:18:17]* betz[m]1 has joined #aegir
[02:18:22]* fndtn357[m] has joined #aegir
[02:18:22]* memtkmcc[m] has joined #aegir
[02:18:23]* bgm[m] has joined #aegir
[02:18:24]* andybatey[m] has joined #aegir
[04:38:31]<bgm[m]>The Aegir nginx default vhost has this: "add_header Access-Control-Allow-Origin *;" Does anyone know why it's there? Isn't it a bit risky?
[06:32:53]* shaneonabike has left #aegir ()
[06:52:06]<colan[m]>bgm: run `git blame` on it to see if you can track down the corresponding issue?
[07:14:14]<bgm[m]>colan: Yikes. Thanks for suggesting that. I was incorrectly double-checking in Aegir, and it was being injected by a customization. :-)
[07:18:44]<bgm[m]>it was fixed in 98216d3cbac744debf62689664959099b1d14ae5 almost a year ago :)
[08:46:38]* theMusician has quit (Quit: theMusician)
[09:00:53]* theMusician has joined #aegir
[09:28:43]* theMusician has quit (Quit: theMusician)
[09:48:57]* mstenta has joined #aegir
[10:10:42]* mstenta has quit (Quit: Leaving)