Hi Nikolaos,
Thanks for the information.
And I've put in a PR to update the Fuseki Jetty HTTPS example using the
the one you tested.
Andy
On 07/07/2022 16:38, Nikolaos Beredimas wrote:
Hi Andy,
TL;DR: Password-less PKCS12 passwords just don't work.
After more testing, I couldn't get
Hi Andy,
TL;DR: Password-less PKCS12 passwords just don't work.
After more testing, I couldn't get a password-less PKCS12 certificate to
work, no matter what I tried.
And after reading around I suspect it's not just Jetty that suffers from
this, so there is nothing to be done.
As for the other
I think we should wait for Andy here with further input as he's the
persons who basically designed and implemented all the fancy stuff and
knows better advice for sure.
@Andy Did you read the whole discussion and can you verify that it's
expected behavior that lot's of daily updates lead to
Can't you just provide a keystore password?
https://stackoverflow.com/questions/12862655/using-an-empty-keystore-password-used-to-be-possible
On Thu, Jul 7, 2022 at 11:42 AM Andy Seaborne wrote:
>
> Hi Nikolaos,
>
>
> On 06/07/2022 11:04, Nikolaos Beredimas wrote:
> > While trying to get Fuseki
Hi Nikolaos,
On 06/07/2022 11:04, Nikolaos Beredimas wrote:
While trying to get Fuseki running over https I found this thread from
February
https://jena.markmail.org/message/2kqpd2tlinpdzpna?q=ssl+order:date-backward=1
1. I can confirm the provided xml works (tested on Fuseki 4.5.0)
Thanks
Hi Lorenz,
Would you recommend using tdb1 instead of tdb2 for our use case? What would be
the differences?
We are using fuseki 4.5.0 btw.
Gaspar
> On 6 Jul 2022, at 14:39, Bartalus Gáspár
> wrote:
>
> Hi,
>
> Most of the updates are DELETE/INSERT queries, i.e
>
> DELETE {?s ?p ?oldValue}
