Jeromy Streets
Jeromy Streets
Ah! Considering it was just a quick prototype, I'll wager that I never set it up to compile with the Dockerfile. My first thought is that the forth comment in...
Try this: ```bash docker run -d --name static_auth_test -v /home/user/static_auth:/web -p 8080:8080 auth_test:latest ``` or ```bash docker run -d --name static_auth_test -e FOLDER=/content/html -v /home/user/static_auth:/content/html -p 8080:8080 auth_test:latest ```
I'm curious about your IP address of 10.0.0.0... does it work remotely if you use the results of your "ip addr" on the server machine?
Does it work with "wget" if you pass the "--auth-no-challenge" flag?
Yeah, that is because I didn't finish implementing it. It was just intended to evaluate workflow. I still need to do some research to work with auth challenging; just never...
I'll move it up the priority list and revisit it in the near future.
Not being a Safari user, I can't speak specifically to that browser, but generally speaking, what I think is happening is that the static-file-server is setting the "Content-Type" HTTP header...
I'll look into this as I get some time. Doesn't sound too difficult, but we will see...
I don't think that will be an issue. When I get some free time I'll dig in a bit deeper. With this, I'm also considering adding in a JSON response...
I'm afraid not. Between work and family, I haven't had any time to work on new features, sadly. I would like to say I will get to it in the...