Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2012] Avoid encoding issues by defining strong rules #551

Closed
icinga-migration opened this issue Oct 13, 2011 · 3 comments
Closed

[dev.icinga.com #2012] Avoid encoding issues by defining strong rules #551

icinga-migration opened this issue Oct 13, 2011 · 3 comments
Labels
enhancement

Comments

@icinga-migration
Copy link

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

Created by tgelf on 2011-10-13 16:35:19 +00:00

Assignee: (none)
Status: Closed (closed on 2014-07-19 14:05:10 +00:00)
Target Version: (none)
Last Update: 2014-07-19 14:05:10 +00:00 (in Redmine)

As encoding issues are causing trouble in Icinga-Web since ever, it would be great if the Icinga-Web team could bring in their wishes and ideas in feature #2011 (core). Clear guidelines will make life easier for all involved developers.
@icinga-migration
Copy link
Author

Updated by jmosshammer on 2012-02-23 14:31:20 +00:00

  • Priority changed from High to Normal

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2013-04-08 20:18:35 +00:00

do we have encoding issues?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-07-19 14:05:10 +00:00

  • Status changed from New to Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@icinga-migration