-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BasicAuth fails in scary ways when using Classic() + static content #19
Comments
This is as designed. Things in the public folder should be treated as On Thu, Jun 11, 2015, 11:22 AM Geoff Franks [email protected]
|
That should be made more apparent in the README then, as
makes it seem like every request to the app will then be authenticated. |
Based on the readme, I should be able to do something like:
However, when serving static files via "./public" under Classic mode, none of the static files are authenticated, unless their content does not exist (all content that exists is not subject to basic auth).
You can verify the tests by modifying them like this:
If the "public/foo" file exists, tests fail with this:
If "public/foo" does not exist, tests pass:
The text was updated successfully, but these errors were encountered: