XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER2
    • EAP_EWP 5.1.1
    • Seam2
    • None
    • Release Notes
    • Hide
      A multipart request was not parsed correctly if CRLF+CRLF (Carriage Return Line Feed) in the header line was separated at the buffer boundary; that is, the header buffer ended with CRLF and the following byte was CRLF. This caused a MultipartRequest error and excessive CPU memory usage. Such multipart request is now parsed correctly and the error no longer occurs.
      Show
      A multipart request was not parsed correctly if CRLF+CRLF (Carriage Return Line Feed) in the header line was separated at the buffer boundary; that is, the header buffer ended with CRLF and the following byte was CRLF. This caused a MultipartRequest error and excessive CPU memory usage. Such multipart request is now parsed correctly and the error no longer occurs.
    • Documented as Resolved Issue
    • NEW

      Multipart request is not parsed correctly when CRLF+CRLF in header line is separated at buffer boundary - buffer ends with [header]CRLF, next byte is CRLF which hasn't been read yet. This parameter is not being parsed correctly.

            mnovotny@redhat.com Marek Novotny
            rhn-support-tkimura Takayoshi Kimura
            Eva Kopalova Eva Kopalova (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: