@Christian
I'm so sorry. I don't know how this sneaked into the code and especially
how I could overlook it for two hours this morning.
Maybe because of Friday ...
Of course it works as it should. Thanks.
@Felix
Yes your pattern sounds meaningful and I often used the approach.
Nowadays I'm
Hi Marco,
my preferred setup is to use a reverse proxy in front of basex.
This would allow you beside other advantages to completely free basex
from serving static files.
Famous http servers like Apache or NGINX could act as reverse proxies.
This is a sample NGINX configuration snippet:
Hi George,
I did some quick tests, but I didn’t manage to reproduce the problem.
Do you think you could build a little self-contained example for us,
e.g. in Java, that shows what goes in wrong?
Thanks in advance,
Christian
PS: I’ll be offline from May 7-21, so it might take a while for me to
Hi Marco,
Does the behavior change if you remove output:method("html")?
Cheers,
Christian
> declare
> %rest:path("/dasbox/ui/resources/{$resource=.+}")
> %rest:GET
> %output:method("html")
> function ui:resources($resource as xs:string){
> let $path := file:base-dir() || 'resources/'
Hi Christian,
I tried the approach of serving static web resources from RestXQ.
First I encountered a problem related to my js files being served to the
browser as b64 encoded and the browser isn't able to interpret the script.
So I modified the code in order to recognize text resources and
I'm trying to create an environment where I can have mutliple BaseX
Servers, and I can run 2-3 complex queries on them at a time. However, I
want to have the ability to stop a running XQuery script for any reason.
I assumed that's what would happen if I KILL the session using a BaseX
client.
6 matches
Mail list logo
