Mule
  1. Mule
  2. MULE-5085

Cookie received from an outbound HTTP endpoint throws exception in inbound HTTP

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 3.0.0-RC3
    • Fix Version/s: None
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-7243HTTP Connector maps incorrect URLs to HTTP endpoints instead of throwing an exception
      MULE-6500Convenient attribute (throwExceptionOnStatus) for http:outbound-endpoint
      MULE-6196HTTP message receiver is using the wrong endpoint
      MULE-8322Http outbound-endpoint send multiple headers "Cookie"
      MULE-4582Multicast inbound endpoints do not receive data.
      MULE-6705NoSuchMethodError in Tomcat embedded MULE when executing http:set-cookie
      MULE-4382Provides expression evaluation for cookie values set on an HTTP outbound-endpoint
      MULE-2416Inbound Streaming http endpoint does not work
      MULE-8211Until-successful not working with an http outbound endpoint
      MULE-7455Inconsistent payload type when calling http endpoint from a flow with http inbound endpoint

      Description

      In an HTTP bridge, if the remote host sends one cookie back (with Set-Cookie) the inbound HTTP dies when the MuleMessageToHttpResponse gets applied:

      Failed to process request, see root exception cause for details: Invalid cookiesObject. Only class org.apache.commons.httpclient.Cookie[] and interface java.util.Map are supported

      This happens because the set-cookie header contains a String.

      Temporary fix consists in removing the set-cookie property in the response phase.

        Activity

        Hide
        Ramiro Rinaudo added a comment -

        Is this still an issue? Can you provide us a sample config?

        Show
        Ramiro Rinaudo added a comment - Is this still an issue? Can you provide us a sample config?
        Hide
        David Dossot added a comment -

        I don't have access to the environment where this was occurring anymore. Since it is super old on a very early release of Mule 3, plus no-one else faced it, I think we can close.

        Show
        David Dossot added a comment - I don't have access to the environment where this was occurring anymore. Since it is super old on a very early release of Mule 3, plus no-one else faced it, I think we can close.
        Hide
        Ramiro Rinaudo added a comment -

        Reopen is needed

        Show
        Ramiro Rinaudo added a comment - Reopen is needed

          People

          • Assignee:
            Unassigned
            Reporter:
            David Dossot
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development