You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment files (e.g. images) placed in the [IXPM_URL]/public directory for use by IXP-Manager are also publicly (not-logged-in) accessible by URL. It would be good to have an analogous [IXPM_URL]/private directory which would be a clearly understood place where IXP-Manager can load images, etc from for a logged in user only (checks login cookie/session). I guess something similar could be achieved by the far more complex method of "wrapping" content inside files with smarty logic in the views directory, but I believe as a simple (and easy-to-understand) option for "non-publicly-viewable" stuff this would also be useful. Example use-case: image files for embedding in documentation pages suitable for logged in users, but not for public browsing...
The text was updated successfully, but these errors were encountered:
Which is not a dumping ground by the way - just medium term storage rather than allowing many issues to build up which reflect poorly on the project at first glance.
At the moment files (e.g. images) placed in the
[IXPM_URL]/public
directory for use by IXP-Manager are also publicly (not-logged-in) accessible by URL. It would be good to have an analogous[IXPM_URL]/private
directory which would be a clearly understood place where IXP-Manager can load images, etc from for a logged in user only (checks login cookie/session). I guess something similar could be achieved by the far more complex method of "wrapping" content inside files with smarty logic in the views directory, but I believe as a simple (and easy-to-understand) option for "non-publicly-viewable" stuff this would also be useful. Example use-case: image files for embedding in documentation pages suitable for logged in users, but not for public browsing...The text was updated successfully, but these errors were encountered: