Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-469

Content type not set accouring to Http specification, RFC 2616

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.5.5
    • Fix Version/s: 1.5.6
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Sender IBM WebSphere 6.1 reciever Oracle 10.1.3.4

      Description

      the AxiomSoapMessage and the SaajSoapMessage set the content-type character-set incorrectly.
      The character set is surrounded by double quotes i.e "ISO-8859-1". the specification however states, $14.17 and $3.7 clearly state that this is not allowed. Although most servers do not complain about it, the one i use does

      Since the implementation is not confirming to specifications, i would say it's a bug.

      Pieter

        Attachments

          Activity

            People

            • Assignee:
              arjen.poutsma Arjen Poutsma
              Reporter:
              pieni Pieter van der Meer
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: