Ian Eure

wee-slack's fix for this: wee-slack/wee-slack#857 I don't currently have time to figure out what they're doing and implement it here, but maybe that'll help someone who does.

Bump. Anyone had a chance to look? Is this actually working for anyone?

> @ieure This fix mentioned here is related to xoxc tokens and it is already fixed in emacs-slack via #552. Please double check the `:token` and the `:cookie` parameters you...

> So there seems to be some sort of differences between curl versions in how they send up multiple cookie headers. Can you compare good / bad output with `curl...

I'm open minded here, but I'm skeptical that the root issue here is curl versions, just based on cURL being a 26-year-old, widely used tool for a standard protocol, vs....

> > I can successfully auth on the CLI with it: > > ``` > > curl -vvv -H'Cookie: d=xoxd-...' 'https://api.slack.com/api/rtm.connect?token=xoxc-...' > > ``` > > Are you able to...

> It's probably not a direct curl problem but seems like a problem related to the curl version, the slack api and your operating system combined. Also, as I mentioned,...

Okay, it looks like this is the thing to do: ```go func init() { reg := jsonschema.GetSchemaRegistry() jsonschema.Must(schemaCommon).Register("", reg) jsonschema.Must(schemaInput).Register("", reg) jsonschema.Must(schemaStored).Register("", reg) } ``` This is extremely non-obvious, and...

Okay, nope. That successfully registers the schema, instead of silently doing nothing at all, but actually validating still breaks with: failed to resolve schema for ref I guess I'll just...

Even after #4395, this still doesn't work quite right, because Nginx inside the Docker container and the PHP code have different expectations about the URL structure which can't be reconciled....