Links from ./foo/bar.md to ../baz/foo-bar.md issues about md2conf HOT 4 CLOSED

This is an intentional (security) feature to prevent inadvertently injecting potentially harmful or sensitive content into a document. md2conf defines a base path, and all relative paths must resolve to a path that is identical to or a descendant of the base path. For example, assuming the base path is /root/base/, documents can reference sub1/doc1.md (resolves to resource in child folder /root/base/sub1/doc1.md) or doc2.md (resolves to sibling entry /root/base/doc2.md) but not ../sub3/doc3.md, which would resolve to /root/sub3/doc3.md, which is no longer inside /root/base/.

Currently, the base path is tied to the document. However, I could imagine a feature improvement in which you can configure base path, and relax where references can point to.

from md2conf.

Ok I see. Understood.

In my use case it would be great if there could be a non default switch to bypass this to just allow relative links from the anywhere in the base dir.

from md2conf.

A new command line configuration option --ignore-invalid-url has been added to prevent exceptions when invalid links are encountered. You will still need to export a full document tree to ensure that cross-referencing relative links are resolved (e.g. you need to export document A to ensure that links found in document B that point to document A are resolved).

from md2conf.

Thanks very much!

from md2conf.