Hi Eliot,

Thanks for the pointer. Just recently, we have added query parameters to
the permission layer of BaseX [1], which led to the surprising behavior
that parameters of type "application/x-www-form-urlencoded" are not
detected as form parameters anymore. This is something that needs to be
cleaned up in a future version of BaseX, but it was possible to fix it in
the short term in the DBA code [2].

BaseX 11.7 will be released in January.

Best,
Christian

[1] https://docs.basex.org/12/Permissions#checking_permissions
[2]
https://github.com/BaseXdb/basex/commit/e80d371fa45072b2c4f37a20efe93c4ca56fe2a4



On Wed, Dec 11, 2024 at 6:03 PM Eliot Kimber <eliot.kim...@servicenow.com>
wrote:

> Using 11.6, the DBA app’s “optimize” panel gives this runtime error:
>
> ```
> Stopped at /data1/basex/webapp/dba/databases/db-optimize.xqm, 104/10:
>
> [basex:restxq] Value of "name" must be xs:string, supplied: ().
>
> ```
>
> Must be a simple code bug but I couldn’t find the source in github. Where
> is the source for the DBA app?
>
>
>
> Cheers,
>
>
>
> E.
>
>
>
>
>
> _____________________________________________
>
> *Eliot Kimber*
>
> Sr. Staff Content Engineer
>
> O: 512 554 9368
>
>
>
> *servicenow*
>
>
>
> servicenow.com <https://www.servicenow.com>
>
> LinkedIn <https://www.linkedin.com/company/servicenow> | X
> <https://twitter.com/servicenow> | YouTube
> <https://www.youtube.com/user/servicenowinc> | Instagram
> <https://www.instagram.com/servicenow>
>

Reply via email to