Project

General

Profile

Actions

Feature #3267

closed

URL Standardization

Feature #3267: URL Standardization

Added by Doug Goldstein over 17 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Resolution:

Description

It'd be nice if there was a choice for creating strict URLs that are separated based on project. i.e. The URL to this page is:

http://www.redmine.org/projects/redmine/issues/new

But then when it's created the URL for the ticket is

http://www.redmine.org/issues/XXXX

If everything related to the project lived under:

http://www.example.org/projects/PROJECT/COMPONENT/OTHERDATA

it would be optimal for people restricting projects based on LDAP groups since Apache and Lighttpd could be configured for that.

Updated by Doug Goldstein over 17 years ago Actions #1

I'm looking now and I notice the activities page on my own site is http://www.example.org/projects/activities/PROJECT but on your site it's http://www.example.org/projects/PROJECT/activities and a few other pages match this. So it's possible you guys are already working on this for 0.9.x

Updated by Jean-Philippe Lang over 17 years ago Actions #2

Some URL refactoring was done in trunk but the tickets URL won't include the project identifier.

Updated by Doug Goldstein over 16 years ago Actions #3

  • Status changed from New to Resolved

This work was completed for the 0.9.x series.

Updated by Felix Schäfer over 16 years ago Actions #4

  • Status changed from Resolved to Closed

Closing as I don't think we will ever have a pattern where everything belonging to a project will be under that project. The reason mentioned is access control, that should be solved by a custom authentication plugin.

Actions

Also available in: PDF Atom