Garry Dolley

I was having the same issue, in 2023! Adding `'access-token', 'token-type', 'client', 'expiry', 'uid'` to my `expose` headers in `config/initializers/cors.rb` saved the day 🙏🏻

It's hard to find something that does token auth with a Rails 7 backend these days. All the new frameworks want to sell you on their serverless JS-only toys. But...

You still need `expose: ['access-token', 'token-type', 'client', 'expiry', 'uid']` in there

I have fetching from external URLs working in my fork; specifically I needed the key included in EXT-X-KEY to be fetched externally, not over IPFS. The commit that implements that...

I also want to use devise-token-auth but my new app is Rails 7.1.1 😭

I found this fork: https://github.com/single-stop-tony/devise_token_auth It makes a slight change to a part of the serialization and updated the gem spec to allow installation with Rails 7.1. No idea if...

This also hit me in a new Rails 6.1 app. Being able to deliver exception notifications in the background is important, and we use Sidekiq to back ActiveJob. I haven't...

I see the following in my logs: ``` opendkim[15609]: 0A5D11EEF20: failed to parse authentication-results: header field opendkim[15609]: 0A5D11EEF20: bad signature data ``` from a particular sender that our mail server...

I've been reading about it just now: https://pypi.org/project/dkimpy-milter/ Looks like I can integrate it with my Postfix setup similarly to the way I have OpenDKIM. This might be the replacement...

I was also having this same problem. I forced `@strapi/utils` to be the exact same version as `@strapi/strapi` and then when an `ApplicationError` was thrown, I saw it correctly in...