You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Has it something to do with the way I set it up? I did the original setup (password + import) using an heroku domain, and then added the custom domain.
The root cause of this was that assetpack does some kind of emulated GET request (source: rstacruz/sinatra-assetpack#68) so our authentication filter was breaking it. I've let requests for assets bypass the authentication filters and now it works again. Whew.
Activity
swanson commentedon May 14, 2013
Could you post the git SHA (
git rev-parse HEAD) of the version you are running?aliou commentedon May 14, 2013
Revision 62ddf65.
aliou commentedon May 14, 2013
Weird, just I just logged out and tried again and there were no problem.
swanson commentedon May 14, 2013
Maybe an issue with the browser cache or something? Let me know if you run into it again.
aliou commentedon May 14, 2013
Has it something to do with the way I set it up? I did the original setup (password + import) using an heroku domain, and then added the custom domain.
swanson commentedon May 15, 2013
Now I'm getting this in my dev environment - something weird is happening :(
swanson commentedon May 16, 2013
This is driving me crazy - it's not working on my production instance again.
aliou commentedon May 16, 2013
I just noticed I have two errors in the javascript console:
swanson commentedon May 16, 2013
Yeah - I'm seeing the same thing. Will try to track this down tonight.
swanson commentedon May 17, 2013
The root cause of this was that assetpack does some kind of emulated GET request (source: rstacruz/sinatra-assetpack#68) so our authentication filter was breaking it. I've let requests for assets bypass the authentication filters and now it works again. Whew.