Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-13671

Unable to delete attachments with German Umlaut like Ü, Ä or Ö in the filename

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Medium Medium
    • None
    • 2.9.2
    • None

    • Windows 2003
      Apache Tomcat 6.0.18

      When we try to delete attached files with German Umlaut's like Ü, Ä or Ö in the filename we get this error:

      "You cannot view this page due to inherited restrictions
      Page level restrictions have been applied to a parent of the current page. These restrictions limit access to only certain certain user(s) or group(s) and apply to all pages in the hierarchy underneath the parent. "

      But the there are no restrictions, see attached screenshots. The error is very serios for us! At least we need a workaround!

        1. 1.png
          1.png
          5 kB
        2. 2.png
          2.png
          5 kB
        3. 3.png
          3.png
          16 kB

            [CONFSERVER-13671] Unable to delete attachments with German Umlaut like Ü, Ä or Ö in the filename

            Markus Lepper added a comment -

            Confluence 5.1.5: We could not move files with ":" in the name.
            See CONF-13766 and https://confluence.atlassian.com/display/DOC/Moving+an+Attachment?focusedCommentId=422019628#comment-422019628

            Markus Lepper added a comment - Confluence 5.1.5: We could not move files with ":" in the name. See CONF-13766 and https://confluence.atlassian.com/display/DOC/Moving+an+Attachment?focusedCommentId=422019628#comment-422019628

            Sebastian Lüdtke added a comment -

            Hello people,

            we got a system error when we want to delete a file that contains a german umlaut... I have to access the file over webdav and can delete it there.

            Our Confluence-Version: 5.0.3

            Sebastian Lüdtke added a comment - Hello people, we got a system error when we want to delete a file that contains a german umlaut... I have to access the file over webdav and can delete it there. Our Confluence-Version: 5.0.3

            Susanne Harelius added a comment -

            It works perfectly in confluence 3.1!

            Susanne Harelius added a comment - It works perfectly in confluence 3.1!

            Susanne Harelius added a comment -

            We still have the problem but run version 2.10.1. We will have discussions very soon about when to upgrade - if we upgrade soon then no sense in spending time on this. Thanks!!

            Susanne Harelius added a comment - We still have the problem but run version 2.10.1. We will have discussions very soon about when to upgrade - if we upgrade soon then no sense in spending time on this. Thanks!!

            Michael Michael added a comment -

            I reported that issue long time ago, we now run Confluence 3.0.1. Works here now. Hopefully Susanne's problem is solved soon, too.

            Michael Michael added a comment - I reported that issue long time ago, we now run Confluence 3.0.1. Works here now. Hopefully Susanne's problem is solved soon, too.

            Roy Hartono [Atlassian] added a comment -

            Hello Susanne,

            Are you still having this problem? If you do please create a ticket at http://support.atlassian.com and we will try to help you.

            Cheers,
            Roy

            Roy Hartono [Atlassian] added a comment - Hello Susanne, Are you still having this problem? If you do please create a ticket at http://support.atlassian.com and we will try to help you. Cheers, Roy

            Susanne Harelius added a comment -

            We have set URLEncoding="UTF-8" on the server but it still does not work.

            Running 2.10.1. Not possible to edit those documents and not possible to delete them. Is there anything else we can do? Should I add a new issue?

            Susanne Harelius added a comment - We have set URLEncoding="UTF-8" on the server but it still does not work. Running 2.10.1. Not possible to edit those documents and not possible to delete them. Is there anything else we can do? Should I add a new issue?

            Michael Michael added a comment -

            That you a lot for your help! Everything works fine now, you can close the issue! Kind Regards!

            Michael Michael added a comment - That you a lot for your help! Everything works fine now, you can close the issue! Kind Regards!

            Andrew Lynch (Inactive) added a comment - - edited

            Hi Michael,

            It is strongly recommended that you run your Confluence instance with UTF-8 URI encoding if your demographic is primarily German speaking. There are other known issues (e.g. searching) which mean that it would be best to switch to UTF-8 URI encoding. There shouldn't really be any noticeable negative side effects.

            The problem is caused by the fact that the delete link uses a GET rather than a form with POST.
            This should not generally non be used when non-ASCII characters are part of the data transmission and the result is that it is up to the application server to decide what format the data is in; by default, this is ISO-8859-1 in Tomcat, which can lead to problems with other Unicode characters. By setting the request URI encoding to UTF-8 we are instructing Tomcat that all GET requests that it receives are UTF-8 encoded, and as such they can be correctly decoded by Confluence.

            We really should probably be doing a POST in these circumstances, but I have linked this particular case to the umbrella issue of reviewing GET / POST usage in Confluence.
            If there are no objections, I will close this issue as it should be incorporated by CONF-8254.

            Regards,
            Andrew Lynch

            Andrew Lynch (Inactive) added a comment - - edited Hi Michael, It is strongly recommended that you run your Confluence instance with UTF-8 URI encoding if your demographic is primarily German speaking. There are other known issues (e.g. searching) which mean that it would be best to switch to UTF-8 URI encoding. There shouldn't really be any noticeable negative side effects. The problem is caused by the fact that the delete link uses a GET rather than a form with POST. This should not generally non be used when non-ASCII characters are part of the data transmission and the result is that it is up to the application server to decide what format the data is in; by default, this is ISO-8859-1 in Tomcat, which can lead to problems with other Unicode characters. By setting the request URI encoding to UTF-8 we are instructing Tomcat that all GET requests that it receives are UTF-8 encoded, and as such they can be correctly decoded by Confluence. We really should probably be doing a POST in these circumstances, but I have linked this particular case to the umbrella issue of reviewing GET / POST usage in Confluence. If there are no objections, I will close this issue as it should be incorporated by CONF-8254 . Regards, Andrew Lynch

            Michael Michael added a comment -

            "URI Encoding" works, tested it on a local copy of Confluence, but I'm a little bit afraid of side effects!

            Michael Michael added a comment - "URI Encoding" works, tested it on a local copy of Confluence, but I'm a little bit afraid of side effects!

              Unassigned Unassigned
              9168e3332326 Michael Michael
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: