Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.2-EE-GA_P01
    • Fix Version/s: 1.8.3, 1.8.2-EE-GA_P02
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      ICEfaces
    • Affects:
      Compatibility/Configuration
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      <context-param>
           <param-name>com.icesoft.faces.blockingRequestHandler</param-name>
           <param-value>icefaces</param-value>
          </context-param>
      Show
      <context-param>      <param-name>com.icesoft.faces.blockingRequestHandler</param-name>      <param-value>icefaces</param-value>     </context-param>

      Description


      If the application server responds with HTTP OK to the push-server detection request, ICEfaces may configure itself for push-server use even though the push-server is not actually present.

        Activity

        Hide
        Ted Goddard added a comment -
        Show
        Ted Goddard added a comment - See also http://jira.icefaces.org/browse/PUSH-85
        Hide
        Jack Van Ooststroom added a comment -

        Messages sent using the HTTPAdapter are now branded by an X-Powered-By header, in order for the HTTPAdapter itself to determine if communication was with another HTTPAdapter instance. Marking this one as FIXED.

        Show
        Jack Van Ooststroom added a comment - Messages sent using the HTTPAdapter are now branded by an X-Powered-By header, in order for the HTTPAdapter itself to determine if communication was with another HTTPAdapter instance. Marking this one as FIXED.

          People

          • Assignee:
            Jack Van Ooststroom
            Reporter:
            Ted Goddard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: