ICEmobile
  1. ICEmobile
  2. MOBI-1133

Fix boundary marker in Content-Type request header

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Containers
    • Labels:
      None
    • Environment:
      iOS container

      Description

      The boundary property in Content-Type request header contains dashes (-----) before and after the marker. This is not required, running with Android container the dashes are missing and as a consequence the warnings (on Jetty server) are not triggered. Most probably bridgeit-client/ios/icemobile/Shared/NativeInterface.m will need to be modified.

        Activity

        Mircea Toma created issue -
        Mircea Toma made changes -
        Field Original Value New Value
        Description The boundary property in _Content-Type_ request header contains dashes (-----) before and after the marker. This is not required, running with Android container the dashes are missing and as a consequence the warnings (on Jetty server) are not triggered. Most probably bridgeit-client/ios/icemobile/Shared/NativeInterface.m will need to be modified. The boundary property in Content-Type request header contains dashes (-----) before and after the marker. This is not required, running with Android container the dashes are missing and as a consequence the warnings (on Jetty server) are not triggered. Most probably bridgeit-client/ios/icemobile/Shared/NativeInterface.m will need to be modified.
        Patrick Corless made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Mircea Toma
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: