Ability to configure own headers for the HTTP request about ahoy.js

[ankane]

Just added the ability to do ahoy.configure({headers: ...}) on master.

[krsyoung]

Hey @Startouf, I'm facing the same problem due to JWT. I'm using jwt_sessions as my authentication framework which authentications via a Authorization header.

I ended up forking ajoy.js and implementing support for headers as an additional configuration parameter. You can take a look here under the issue_23 branch: https://github.com/krsyoung/ahoy.js/tree/issue_23

It is pretty bad at the moment but works. In my frontend Vue code I just make a call to set the header once the user has authenticated:

// this.$ahoy is my ahoy instance
this.$ahoy.setHeader('Authorization', 'Bearer: ' + accessToken)

My situation is even more complicated as I need to decode the token on the backend before I can access the current user. I solved this by creating a custom user method for ahoy (called ahoy_user) that manually performs the decode and then returns the user.

What did you end up doing? Could my branch work for you?

[Startouf]

I'm reading the JWT token + user ID from custom headers named X-user-Token and X-user-email so I'm not sure your branch would work if you are just reading from Authorization

I am using the simple_token_authentication gem

[krsyoung]

Ah, the change I made in my branch is really just to allow ahoy.js to support any arbitrary headers. I think in your case it would be as simple as:

// set customer HTTP headers for ahoy
ahoy.setHeader('X-user-token', 'xxx')
ahoy.setHeader('X-user-email', 'xxx')

I also ate a lot of turkey over the past couple of days so I can't really say I'm 100% confident!

[golmansax]

@krsyoung I started using your branch and it works great. One thing is I needed to set useBeacon to false to get the headers to send when tracking events.

Since it seems like there's sufficient interest in this feature, can we submit a pull for this?

[krsyoung]

I'm game if @ankane is supportive.

Good call on the useBeacon @golmansax!