Hey,
2016-07-12 20:39 GMT+02:00 K. Frank <kfrank2...@gmail.com>:
> >> On the other hand, a link (that evaluates) to:
> >>
> >> http://localhost/mixed_links/static_links/link1.html
> >>
> >> does not successfully link to the file. The ";" syntax does have an
> >> effect, however. If I deploy with "--docroot="."", the above link
> returns
> >> a 404, while if I deploy with "--docroot=.;/static_links", the above
> link
> >> gets processed as an internal path in my application (but wthttpd does
> >> not serve the link1.html file as static content).
> >
> > Not quite so:
> > - with "--deploy-path=/mixed_links/ --docroot="."", Wt will interpret
> this
> > request as an internal path (as it matches the deploy-path of an
> > application)
>
> This isn't what I see -- I've tried to repeat the test quite carefully.
>
Sorry, I was wrong indeed, you're initial statement is correct. Although
the path matches the deploy-path, the request is application will use 'ugly
internal paths' and thus interpret this path as a static file request
instead.
> > I hope the clarifications help.
>
> Yes, thanks very much.
>
Even though they were not clarifying ;-)
Still, are things now still unclear?
Regards,
koen
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
