Static assets URL parser wrong about panel

[philippjfr]

Cannot reproduce this, I just ran panel serve app.py --static-dirs assets=doc and then placed an index.html at doc/_static/index.html, which loaded just fine:

[skaller]

interesting .. let me see if I can get some screenshots from my client (and a version number .. how do you get that?)

[skaller]

ok we have Panel serve 1.2.3 .. installed using Conda ..

[skaller]

We managed to get 1.3.6 .. still same issue ..

[philippjfr]

As I said, I cannot reproduce. You'll have to provide more detail, such as operating system and also investigate the permissions structure for the files. Can you reproduce with a different directory that you newly created? Internally we simply use the Tornado StaticFileHandler so it's very unlikely Panel itself is at fault here.

[skaller]

AH! You aren't doing the same test, that's why you're not reproducing it perhaps. You're putting the URL in the browser search line. That works for us too. What fails is if the URL is in an <a href="...">...</a> tag and you click on it.

In our case that tag is generated by Quarto blog generator, and the click works just fine if we start with the browser pointing at the top level of the blog (i.e. the index page) as a file. But if we point the browser at a the http connection running Panel, we can go into assets/index.html just fine, but clicking on the linking in that page fails.

I'll send more data shortly. We spent all night here trying to get conda-forge to install the latest version. The base conda package is 1.2.3 which is way out of date.

[skaller]

Just to be clear, the top level entry into assets works fine but a link in that file to an indiex.html in a subdirectory fails with a 403 and the web server reports, on the command line, that the directory is not a file .. leaving out the index.html. The browser search line also shows the wrong link, i.e. without the index.html at the end. I don't understand this because the construction of the link is done by the browser but BOTH safari and chrome fail the same way.

[skaller]

It could be our CDM system. We have only tried with the live online service, we haven't tried with localhost. I'll get my client to test that, Thanks for holding!

[skaller]

I have made a simple test case, and it works just fine. But it fails with the quarto generated html. On the other hand the quarto html works fine if its index is the entry. None of this makes any sense to me, since the browser should just be adding a prefix to the anchor href, and the quarto anchor's href is, in my opinion, correct.

In any case I apologise for raising this issue, and thank you for your help, and am now closing it.