Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1198

SolusVM: Responses from SolusVM do not escape ampersands

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-b1
    • Fix Version/s: 3.2.0-b2
    • Component/s: Modules
    • Labels:
      None

      Description

      Responses from SolusVM are not properly encoded XML, and can cause SimpleXML parser to fail.

      For instance, if a client has a company name with an ampersand (&), less than (<), or greater than (>) symbol in their name, SolusVM will return these fields in its response unencoded.

      We should at least fix the ampersand, as that is not as uncommon to have. We can't do much with the other unencoded characters at this time.

        Activity

        tyson Tyson Phillips (Inactive) created issue -
        tyson Tyson Phillips (Inactive) made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Description Responses from SolusVM are not properly encoded XML, and can cause SimpleXML parser to fail.

        For instance, if a client has a company with an ampersand (&), less than (<), or greater than (>) symbol in their name, SolusVM will return these fields in its response unencoded.

        We should at least fix the ampersand, as that is not as uncommon to have. We can't do much with the other unencoded characters at this time.
        Responses from SolusVM are not properly encoded XML, and can cause SimpleXML parser to fail.

        For instance, if a client has a company name with an ampersand (&), less than (<), or greater than (>) symbol in their name, SolusVM will return these fields in its response unencoded.

        We should at least fix the ampersand, as that is not as uncommon to have. We can't do much with the other unencoded characters at this time.
        tyson Tyson Phillips (Inactive) made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            tyson Tyson Phillips (Inactive)
            Reporter:
            tyson Tyson Phillips (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              2/May/14