grizzly
  1. grizzly
  2. GRIZZLY-996

content-length header should be processed as long

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1
    • Component/s: None
    • Labels:
      None

      Description

      when parsing, serializing HTTP headers, we should assume content-length is Java long, not int.
      In most cases we process it right, but in http-server module there is a place, where we take it as int.
      We need to fix that and add API to the Request/Response to work with content-length as long value.

        Activity

        Hide
        oleksiys added a comment -

        Project: grizzly
        Repository: hg
        Revision: 1662
        Author: oleksiys
        Date: 2011-04-08 14:44:19 UTC
        Link:

        Log Message:
        ------------
        fix issue #996
        http://java.net/jira/browse/GRIZZLY-996
        "content-length header should be processed as long"

        Show
        oleksiys added a comment - Project: grizzly Repository: hg Revision: 1662 Author: oleksiys Date: 2011-04-08 14:44:19 UTC Link: Log Message: ------------ fix issue #996 http://java.net/jira/browse/GRIZZLY-996 "content-length header should be processed as long"

          People

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

            Dates

            • Created:
              Updated:
              Resolved: