GrabNet | Generative model to generate realistic 3D hands | Machine Learning library

I think you forgot to start a php tag which means one of your { brackets is in the javascript string and not in php. Due to that, the closing bracket } of is is unexpected because it never started.

Try adding a on the first line where I created the arrow on your screenshot:

I managed to find out that the issue was not caused by the Nginx configuration file but instead was down to a Cloudflare setting (https://community.cloudflare.com/t/how-do-i-disable-tls-1-0/2670/10).

I used this repo to find out that the server was not at fault (testing the servers ip_address:port) - https://github.com/drwetter/testssl.sh

The command I used was "/bin/bash testssl.sh 256.98.767.762:443" (not my servers real ip)

• 401 is the Access denied status code.

• so in your htaccess file write:

  ErrorDocument 401 /401.html

the /401.html is a page that you create, you can name it whatever you want

Sometimes the htaccess commands work inside modules.

Try this one.

i could achieve it using

The Apache docs for htaccess can be tricky to figure out in the beginning. Htaccess has been around since the first web server and morphed along the way into what we fiddle with now. I've had to figure out things like this very many times. There are surely several ways to accomplish what you want, which makes it even more confusing. Here's a .htaccess file that should do the trick for you:

it is making my assets load from a wrong directory, it is appending the details keyword when loading the assets

Of course this happens, because that’s simply how resolving a relative URL to an absolute one works. The address of the current document is taken into account.

And the easiest solution, is to refer all your assets from the domain root, with a leading slash.

If your stylesheet is located at http://www.vidtest.com/assets/css/bootstrap.min.css, then you simply use /assets/css/bootstrap.min.css to refer to it, instead of assets/css/bootstrap.min.css

The leading slash means “relative to the domain root”, and therefor the path of the current document doesn’t affect relative URL resolution any more.

Keep this rule just below first RewriteEngine On line to enforce http -> https and www:

Since there are two different scenarios (one or two url fragments), we can set up two rules for that: