Thank you Francis - the "try" line was key :)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,261396,261495#msg-261495
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I'm using the Angular ui-router which uses states to control the routes.
Meaning that all request should serve the same index.html file, and the
JavaScript worries about loading in appropriate content.
The .htaccess rules that control the same thing are below:
RewriteEngine On
# Required t
Thanks for the response! I made that change, and I think what was really
giving the 404 was that I had changed permissions on the `index.html` file,
but not on the var/www/ folder, which I needed so that the nginx user group
could access it. Thanks!
Posted at Nginx Forum:
http://forum.nginx.org/r
I have a pretty standard test nginx configuration file
(/etc/nginx/sites-available/default) that was configured to serve a sample
html document.
Here's the modified portion of the configuration file.
upstream auth{
server 127.0.0.1:3000;
}
server {
listen 80 default_server;