jersey
  1. jersey
  2. JERSEY-1088

Content type header is not being set properly in async scenarions

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0-m02
    • Fix Version/s: 2.0-m05, 2.0
    • Component/s: None
    • Labels:
      None

      Description

      Currently the the header is properly set only for the sync Java-based case as the header update is now done in MultipleMethodAcceptor. This does not work for async scenarios properly. I can provide a quick-fix and set the header in the ApplicationHandler.writeResponse(...) if not set, but we should come up with a final common solution that will work for all scenarios correctly.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Marek Potociar
              Reporter:
              Marek Potociar
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 12 hours
                12h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 30 minutes Time Not Required
                1h 30m