ICEmobile
  1. ICEmobile
  2. MOBI-291

Standalone HTML example return throws exception

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1 Final
    • Fix Version/s: 1.1 Final
    • Component/s: None
    • Labels:
      None
    • Environment:
      ICEmobileSpring + Blackberry device

      Description

      To reproduce, go to the standalone HTML sample page in Blackberry from the ICEmobilespring application. Record an audio file, then upload. When you click on the return link, you'll get a 404 error and no page is displayed.

      The requests from the client are

      [6.4552 11:33:03.309s] -- GET /icemobilespring/resources/media/clip.mp4 HTTP/1.1
      [17.625 11:33:14.479s] -- POST /icemobilespring/jsonmic HTTP/1.1
      [17.783 11:33:14.637s] -- 1`!a-%A0<HF��J���h�J�D[��0?�f�9��<B&���Jw���5DP���
      [22.390 11:33:19.244s] -- GET /icemobilespring/#icehtml HTTP/1.1
      [22.917 11:33:19.771s] -- GET /favicon.ico HTTP/1.1


      The responses are:

      6.4677 11:33:03.321s] HTTP/1.1 404 Not Found
      [18.115 11:33:14.969s] HTTP/1.1 200 OK
      [22.400 11:33:19.254s] HTTP/1.1 404 Not Found
      [22.919 11:33:19.773s] HTTP/1.1 200 OK

      (as an aside clip.mp4 is also not found, but that is missing for all devices and doesn't harm any other devices)

      But this request is the one that fails:
       GET /icemobilespring/#icehtml HTTP/1.1

        Activity

        Hide
        Ted Goddard added a comment -

        There may be an alternate approach for the return link that is compatible with BlackBerry.

        Show
        Ted Goddard added a comment - There may be an alternate approach for the return link that is compatible with BlackBerry.
        Hide
        Ted Goddard added a comment -

        I have just tested the icemobilespring HTML example on the BlackBerry stock browser, and it works well. I believe the container must not be stripping off the # marker in the URL and is instead forwarding it to the server.

        Show
        Ted Goddard added a comment - I have just tested the icemobilespring HTML example on the BlackBerry stock browser, and it works well. I believe the container must not be stripping off the # marker in the URL and is instead forwarding it to the server.
        Hide
        Greg Dick added a comment -

        I've checked in a change for the Blackberry Protocol handler that strips off any fragment portion of any request URLs. The fragment portion is meant as a protocol specific subdivision within the main document, and isn't meant to be included in the GET.

        Show
        Greg Dick added a comment - I've checked in a change for the Blackberry Protocol handler that strips off any fragment portion of any request URLs. The fragment portion is meant as a protocol specific subdivision within the main document, and isn't meant to be included in the GET.
        Hide
        Steve Maryka added a comment - - edited

        =20

        Show
        Steve Maryka added a comment - - edited =20

          People

          • Assignee:
            Greg Dick
            Reporter:
            Greg Dick
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: