ICEfaces
  1. ICEfaces
  2. ICE-9256

ResourceRegistry doesn't handle ranged requests properly

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.3
          • Fix Version/s: EE-3.3.0.GA
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces applications serving resources to Android container in Blackberry 10 runtime client.

            Description

            ResourceRegistry code was not handling range requests where the start offset was defined but the end range was not. A request of the form:

            GET /mobileshowcase/javax.faces.resource/92cde6b3-0177-4734-8aba-20a119e82ef7.jsf;jsessionid=5E353DF770A45C6D235D25A97D720DD6 HTTP/1.1
            Range: bytes=4832-
            User-Agent: io-media
            Host: 50.50.50.154:9090
            Accept: */*
            Icy-MetaData: 1


            Was not properly setting the response status as 206.

              Issue Links

              blocks

              Task - A task that needs to be done. MOBI-674 BlackBerry 10 investigation

              • Major - Major loss of function.
              • Resolved

                Activity

                Ascending order - Click to sort in descending order
                Greg Dick created issue -
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #34934 Thu May 09 12:17:28 MDT 2013 greg.dick ICE-9256 Range check now handles missing rangeEnd field
                Files Changed
                Commit graph MODIFY /icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/application/ResourceRegistry.java
                Greg Dick made changes -
                Field Original Value New Value
                Link This issue blocks MOBI-674 [ MOBI-674 ]
                Hide
                Permalink
                Greg Dick added a comment -

                Existing code wasn't properly interpreting the case when the endRange value was missing.

                Show
                Greg Dick added a comment - Existing code wasn't properly interpreting the case when the endRange value was missing.
                Greg Dick made changes -
                Status Open [ 1 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #36098 Mon Jun 10 14:25:30 MDT 2013 philip.breau porting ICE-9256 Range check now handles missing rangeEnd field rev 34934
                Files Changed
                Commit graph MODIFY /icemobile/branches/icemobile-1.3.0/icemobile/spring/src/main/java/org/icemobile/spring/handler/RangingResourceHttpRequestHandler.java
                Repository Revision Date User Message
                ICEsoft Public SVN Repository #36099 Mon Jun 10 14:26:10 MDT 2013 philip.breau porting ICE-9256 Range check now handles missing rangeEnd field rev 34934
                Files Changed
                Commit graph MODIFY /icemobile/trunk/icemobile/spring/src/main/java/org/icemobile/spring/handler/RangingResourceHttpRequestHandler.java
                Ken Fyten made changes -
                Status Resolved [ 5 ] Closed [ 6 ]

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved: