From d56768902e227149fa33609d7e287efd710a99f4 Mon Sep 17 00:00:00 2001 From: Mattias Reichel Date: Mon, 25 Mar 2024 22:56:05 +0100 Subject: [PATCH] docs(typo): Set correct file extension (#443) --- src/main/docs/guide/resources.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/docs/guide/resources.adoc b/src/main/docs/guide/resources.adoc index eaeb109a3b..caec97f08c 100644 --- a/src/main/docs/guide/resources.adoc +++ b/src/main/docs/guide/resources.adoc @@ -19,7 +19,7 @@ Take a look at the http://asset-pipeline.com/manual[documentation] for the asset If you do not want to use the Asset-Pipeline plugin, you can serve the static assets from directories `src/main/resources/public` or `src/main/webapp`, but the latter one only gets included in WAR packaging but not in JAR packaging. -For example, if you had a file stored at `/src/main/resources/public/images/example.png` and your Grails application was running on port 8080, then you could access the file by navigating to http://localhost:8080/static/images/example.jpg[http://localhost:8080/static/images/example.jpg]. +For example, if you had a file stored at `/src/main/resources/public/images/example.jpg` and your Grails application was running on port 8080, then you could access the file by navigating to http://localhost:8080/static/images/example.jpg[http://localhost:8080/static/images/example.jpg]. ==== Cache Configuration for Static Resources