Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Configuration of static backend should deny setups known to create issues #89

Open
arkascha opened this issue Jan 1, 2015 · 0 comments
Open

Configuration of static backend should deny setups known to create issues #89

arkascha opened this issue Jan 1, 2015 · 0 comments
Labels
enhancement

Comments

@arkascha
Copy link
Contributor

arkascha commented Jan 1, 2015

The configuration option of the 'static backend' should not only reflect the resulting URL namespace (as it already does), but also deny such setups that are known to create issues.

  • configuring the base URL to point to exactly that folder where the OC code is installed
  • configuring the base URL to point to a folder containing any physical files/folders
  • or more general: configuring the base URL to point to a base inside which Shorty IDs are not guaranteed to be unique.

The reason here is potential name conflict with existing files/folders.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arkascha