This is an automated email from the ASF dual-hosted git repository.
afs pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/main by this push:
new dc916d796 Update links previously to fuseki-main.html to
fuseki-plain.html
dc916d796 is described below
commit dc916d7967846e213ca3b63fc6132f15a7fe3c9a
Author: Øyvind Gjesdal <[email protected]>
AuthorDate: Wed Aug 5 11:05:43 2026 +0200
Update links previously to fuseki-main.html to fuseki-plain.html
File renamed in
https://github.com/apache/jena-site/commit/21ce90f0892545f585c4c464caf0beffb8441a2f
---
source/documentation/fuseki2/fuseki-config-endpoint.md | 2 +-
source/documentation/fuseki2/fuseki-configuration.md | 4 ++--
source/documentation/fuseki2/fuseki-data-access-control.md | 2 +-
source/documentation/fuseki2/fuseki-docker.md | 2 +-
source/documentation/fuseki2/fuseki-embedded.md | 2 +-
source/documentation/fuseki2/fuseki-main-security.md | 13 -------------
source/documentation/fuseki2/fuseki-server-info.md | 2 +-
7 files changed, 7 insertions(+), 20 deletions(-)
diff --git a/source/documentation/fuseki2/fuseki-config-endpoint.md
b/source/documentation/fuseki2/fuseki-config-endpoint.md
index faa4448cd..b2f0754e4 100644
--- a/source/documentation/fuseki2/fuseki-config-endpoint.md
+++ b/source/documentation/fuseki2/fuseki-config-endpoint.md
@@ -150,7 +150,7 @@ or with TDB storage, with `--update`):
which adds requests that can change the data.
-New operations can be added by programmatic setup in [Fuseki
Main](/documentation/fuseki2/fuseki-main).
+New operations can be added by programmatic setup in [Fuseki
Main](/documentation/fuseki2/fuseki-plain).
## Dispatch
diff --git a/source/documentation/fuseki2/fuseki-configuration.md
b/source/documentation/fuseki2/fuseki-configuration.md
index bd47d6bfc..cebbe756c 100644
--- a/source/documentation/fuseki2/fuseki-configuration.md
+++ b/source/documentation/fuseki2/fuseki-configuration.md
@@ -15,11 +15,11 @@ For Fuseki Full (webapp with UI):
`FUSEKI_BASE` is the location of the [Fuseki run area](./fuseki-layout.html).
-For [Fuseki Main](fuseki-main.html):
+For [Fuseki Main](fuseki-plain.html):
1. The command line, using `--conf` to provide a configuration file.
2. The command line, using arguments (e.g. `--mem /ds` or `--tdb2 --loc DB2
/ds`).
-3. [Programmatic configuration](fuseki-main.html#build) of the server.
+3. [Programmatic configuration](fuseki-embedded.html#build) of the server.
See [Fuseki Security](fuseki-security.html) for more information on security
configuration.
diff --git a/source/documentation/fuseki2/fuseki-data-access-control.md
b/source/documentation/fuseki2/fuseki-data-access-control.md
index 0b1e9f497..ff40f8eb8 100644
--- a/source/documentation/fuseki2/fuseki-data-access-control.md
+++ b/source/documentation/fuseki2/fuseki-data-access-control.md
@@ -6,7 +6,7 @@ Fuseki can provide access control at the level on the server,
on datasets,
on endpoints and also on specific graphs within a dataset. It also
provides native https to protect data in-flight.
-[Fuseki Main](/documentation/fuseki2/fuseki-main.html)
+[Fuseki Main](/documentation/fuseki2/fuseki-plain.html)
provides some common patterns of authentication and also
[Graph level Data Access Control](#graph-acl) to provide control over the
visibility of
graphs within a dataset, including the union graph of a dataset and
diff --git a/source/documentation/fuseki2/fuseki-docker.md
b/source/documentation/fuseki2/fuseki-docker.md
index 873a2c5bc..9d9c13a3a 100644
--- a/source/documentation/fuseki2/fuseki-docker.md
+++ b/source/documentation/fuseki2/fuseki-docker.md
@@ -7,7 +7,7 @@ contains a Dockerfile, docker-compose file, and helper scripts
to
create a docker container for Apache Jena Fuseki.
The docker container is based on
-[Fuseki main](https://jena.apache.org/documentation/fuseki2/fuseki-main)
+[Fuseki main](https://jena.apache.org/documentation/fuseki2/fuseki-plain)
for running a SPARQL server.
There is no UI - all configuration is by command line and all usage by via the
diff --git a/source/documentation/fuseki2/fuseki-embedded.md
b/source/documentation/fuseki2/fuseki-embedded.md
index c39b44875..74694888c 100644
--- a/source/documentation/fuseki2/fuseki-embedded.md
+++ b/source/documentation/fuseki2/fuseki-embedded.md
@@ -50,7 +50,7 @@ To include an embedded Fuseki server in the application:
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-fuseki-main</artifactId>
- <version>3.x.y</version> <!-- Set the version -->
+ <version>6.x.y</version> <!-- Set the version -->
</dependency>
This brings in enough dependencies to run Fuseki. Application writers are
strongly
diff --git a/source/documentation/fuseki2/fuseki-main-security.md
b/source/documentation/fuseki2/fuseki-main-security.md
deleted file mode 100644
index 3d39e374b..000000000
--- a/source/documentation/fuseki2/fuseki-main-security.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Security in Fuseki2 server
----
-This page covers security for Fuseki Main.
-
-See other [documentation](./fusek0-security.html) for the webapp packaging of
Fuseki.
-
-## Serving RDF
-
-For any use of users-password information, and especially HTTP basic
-authentication, information is visible in the HTTP headers. When serving RDF
and SPARQL requests, using HTTPS is necessary to avoid snooping.
-Digest authentication is also stronger over HTTPS
-because it protects against man-in-the-middle attacks.
\ No newline at end of file
diff --git a/source/documentation/fuseki2/fuseki-server-info.md
b/source/documentation/fuseki2/fuseki-server-info.md
index 79d191f4b..94d688f68 100644
--- a/source/documentation/fuseki2/fuseki-server-info.md
+++ b/source/documentation/fuseki2/fuseki-server-info.md
@@ -13,7 +13,7 @@ format. The Prometheus data includes both database and JVM
metrics.
## Endpoints
The following servers endpoints are available. They are present in Fuseki/UI;
-they need to be enabled with [Fuseki/main](fuseki-main.html), either on the
+they need to be enabled with [Fuseki/main](fuseki-plain.html), either on the
command line or in the server configuration file with a boolean setting.
| Endpoint | Config Property | Usage |
