Replies: 4 comments 8 replies
-
|
I don't follow what you are asking specifically for? We have several deployers already ...
Keep in mind that each deployment exists on it's own You cannot have two |
Beta Was this translation helpful? Give feedback.
-
|
I'm asking for a way to not having to create a properties file (https://jetty.org/docs/jetty/12.1/operations-guide/deploy/index.html#web-application-format-static) to disable dir listing for every static app that I deployed to the same context (e.g. "/"). I guess this is doable only with static app because I don't need to separate each static app into its own context. In this case, the "folder" itself serves as a distinct path for the app already and all of them behave the exact same way (which basically just renders the static content). To be very specific, I'm asking for a way to provide a custom version of this: |
Beta Was this translation helpful? Give feedback.
-
This configuration doesn't make sense to me. Please provide examples of the properties files you have now. |
Beta Was this translation helpful? Give feedback.
-
|
I followed the static deployer setup as seen here: Let's say my Jetty base is: /opt/jetty_base and my webapps directory is webapps. Let's say that the JAR file I created using the example above is mystaticdeployer.jar. If I run "java -jar mystaticdeployer.jar", I can easily drop any static folder to /opt/jetty_base/webapps and they will be accessible via http://host:port/app_folder_name. For example, if I put "app1" and "app2" under "/opt/jetty_base/webapps", I can access them as "http://host:port/app1" and "http://host:port/app2". Now the problem is that by default if I visit the URL "http://host:port/app1/subdir", it will list all the directories under subdir. I don't want that to happen so I have to create an "app1.properties" file with the following content (as suggested here https://jetty.org/docs/jetty/12.1/operations-guide/deploy/index.html#web-application-format-static): What I want to do is to be able to change the behavior of the ResourceHandler for https://github.com/jetty/jetty.project/blob/jetty-12.1.x/jetty-core/jetty-staticapp/src/main/java/org/eclipse/jetty/staticapp/StaticAppContext.java to not allow dir listing. Something like: Could you please tell me how I can do that without overriding StaticAppContext and providing my own jar for the environment as seen in this snippet here from the example provided: I can confirm that I can access both "app1" and "app2" without issues. I just need to have a way to turn off dir listing for both without having to provide "app1.properties" and "app2.properties". |
Beta Was this translation helpful? Give feedback.
-
|
Ah, this is easy, far easier than you suspect. Create a Put any line you want all deployments to the |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this is exactly what I'm looking for and much easier than I expected. Thank you so much. I had no idea that the properties file is environment specific as well and not just application specific.
On Friday, March 13, 2026 at 06:31:29 PM EDT, Joakim Erdfelt ***@***.***> wrote:
Ah, this is easy, far easier than you suspect.
Create a ${jetty.base}/environments/static.properties
Put any line you want all deployments to the static environment to apply.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Keep in mind that you can also create Where So, if you deploy to
The XMLs are applied in alphabetical order. |
Beta Was this translation helpful? Give feedback.
-
|
Of note, the |
Beta Was this translation helpful? Give feedback.
-
|
For completeness, this is documented here: https://jetty.org/docs/jetty/12.1/operations-guide/deploy/index.html#environment-configuration |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure what I did wrong but I created a It only works if I created an Is it possible that the environment-based configuration doesn't work with the embedded server and static environment using the staticapp.jar? Please advise. Thanks. |
Beta Was this translation helpful? Give feedback.
-
This is embedded? Example: import org.eclipse.jetty.staticapp.StaticAppContext;
Path webapps = ...;
Path environments = ...;
Server server = new Server();
ContextHandlerCollection contextHandlerCollection = new ContextHandlerCollection();
server.setHandler(contextHandlerCollection);
StandardDeployer deployer = new StandardDeployer(contextHandlerCollection);
server.addBean(deployer);
DeploymentScanner deploymentScanner = new DeploymentScanner(server, deployer);
server.addBean(deploymentScanner);
deploymentScanner.addWebappsDirectory(webapps);
deploymentScanner.setEnvironmentsDirectory(environments); // This line
// Configure the "static" environment
Environment.ensure("static", StaticAppContext.class);
DeploymentScanner.EnvironmentConfig testConfig = deploymentScanner.configureEnvironment("static");
testConfig.setDefaultContextHandlerClass(StaticAppContext.class);
server.start(); |
Beta Was this translation helpful? Give feedback.
-
|
Just to show how this works in jetty-home / jetty-base. Lets start with creating a new jetty-base ... Lets create a few static webapps. Start the server We can see that the server started, with 3 webapps. Let hit one and see if what the results are ... Yup, that's a directory listing. Lets start server again ... And try accessing one of the static webapps now. Yup, it works. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Jetty version
12.1.7
Jetty Environment
static
Enhancement Description
Hi,
As shown in the examples seen here https://jetty.org/docs/jetty/12.1/programming-guide/server/deploy.html, there is not an easy way to configure a specific environment's context for something like the static deployer. I understand that we have the option to override the StaticAppContext and provide our own setting such as the "dirAllowed" property for the entire server (and not just a specific application via the "app.properties" file). However, that would require us to create our own jar and add it to the classpath.
I wonder if it is possible to provide a more flexible option create the environment dynamically using our own custom StaticAppContext without having to deal with ClassLoader and what not? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions