3.9 Config controller did not check properly config name (I1.1)

XMLWordPrintable

    • Medium
    • None
    • When passing invalid configuration names to the config API that did lead to strange errors not properly logged but disclosing some server paths.
    • None

      problem

      When PUTing invalid configuration names that is leading to a 404 answer containing the full exception content including the stack trace. 

      problem

      Handle such error properly and prevent exception disclosure to end clients.

            Assignee:
            Thomas Lauria
            Reporter:
            Thomas Lauria
            None
            None
            Sasha
            NO-FRONTEND-TESTING NEEDED
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None