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.

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

[dev.icinga.com #11091] Custom navigation items: URL is not escaped/encoded #2277

Closed
icinga-migration opened this issue Feb 4, 2016 · 3 comments
Labels
area/framework Affects third party integration/development bug Something isn't working queue/important Blocks a release or needs immediate attention
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11091

Created by dgoetz on 2016-02-04 15:23:21 +00:00

Assignee: aklimov
Status: Resolved (closed on 2016-02-18 14:10:03 +00:00)
Target Version: 2.2.0
Last Update: 2016-02-18 14:10:03 +00:00 (in Redmine)


Adding a shared navigation and using the macro resolver creates an unencoded URL. For example if the service name contains white space, the url will contain whitespaces instead of %20.

Changesets

2016-02-18 14:01:21 +00:00 by aklimov a83ab2c

Escape URLs of navigation items while rendering them

fixes #11091
@icinga-migration
Copy link
Author

Updated by elippmann on 2016-02-18 11:43:43 +00:00

  • Subject changed from Shared Navigation: Url is not urlencoded to Custom navigation items: URL is not escaped/encoded
  • Category set to Framework
  • Priority changed from Normal to High
  • Target Version set to 2.2.0

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-02-18 12:09:28 +00:00

  • Status changed from New to Assigned
  • Assigned to set to aklimov

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-02-18 14:10:03 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset a83ab2c.

@icinga-migration icinga-migration added queue/important Blocks a release or needs immediate attention bug Something isn't working area/framework Affects third party integration/development labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.2.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/framework Affects third party integration/development bug Something isn't working queue/important Blocks a release or needs immediate attention
Projects
None yet
Development

No branches or pull requests

1 participant