Not able to see private datasets or failed revisions while "logged in"

[zelima]

If a user is logged in and after a while (token expires) tries to take a look at private dataset or pushes new one, a user is not able to see neither of the private dataset, broken revision or it's processing progress - the user is getting 404 instead. The user has to magically guess the reason, got to the main page, log out and log in again.

How to reproduce

• log in and wait until token expires
• create a broken dataset or push a dataset with --private findability
• Visit the link displayed in terminal

Workaround:

• go to the main page datahub.io
• log out
• log in
• Visit to link from terminal again

Expected behavior

• [ ] I'm logged out when token expires
• [ ] I'm notified/suggested that I might need to log in to see the dataset

[AcckiyGerman]

I still see the same message.

[zelima]

@AcckiyGerman should be fixed now (disable caching for css)

[AcckiyGerman]

FIXED. User now have instructions what to do, when he sees the blocked page.