bbaldino
bbaldino
chrome doesn't seem to require the profile information in the offer, which is why we hadn't noticed this before when we were testing h264 with chrome. but we'll need to...
Hm, not sure. There's a good chance the tag is just malformed for some reason. I don't remember much about the expected statsd format. @aaronkvanmeerten any ideas? Have we seen...
Not currently possible from the jibri side, unsure if there's some proxy, etc trick that would do it
Hm, we're running chromedriver `80.0.3987.106` in prod and not seeing any issue? Maybe I'm misunderstanding what requires this.
Ok, just not sure accepting insecure certs is something we'd want to always turn on. Maybe it needs to be configurable.
Can this be done with a chrome flag? Those are configurable now, but I'm not sure if there is an equivalent chrome flag to `ChromeOption#setAcceptInsecureCerts`. @saghul is this still needed?
> I think the right way to fix this is to add a config option in Jibri to set the "base URL". If set we could use that to build...
@damencho any thoughts on this?
i don't think we've published anything under stable yet, though we probably should. @aaronkvanmeerten what's the plan there?
I'm not sure if I'll end up merging this or not. We only officially support Java 8 right now and at some point will probably just make the transition to...