Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15829

JBWEB004248 causes empty reply

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 25.0.0.Final
    • Web (Undertow)
    • None
    • Hide
      • Deploy the example war on the application server, e.g. docker run -v $(pwd)/target/jsp-error-1.0-SNAPSHOT.war:/opt/jboss/wildfly/standalone/deployments/jsp-error-1.0-SNAPSHOT.war -p 8080:8080 jboss/wildfly:25.0.0.Final
      • Send an HTTP request using the CONNECT method to the server, e.g. curl -X CONNECT http://localhost:8080/jsp-error-1.0-SNAPSHOT/
      Show
      Deploy the example war on the application server, e.g.  docker run -v $(pwd)/target/jsp-error-1.0-SNAPSHOT.war:/opt/jboss/wildfly/standalone/deployments/jsp-error-1.0-SNAPSHOT.war -p 8080:8080 jboss/wildfly:25.0.0.Final Send an HTTP request using the CONNECT method to the server, e.g.  curl -X CONNECT http://localhost:8080/jsp-error-1.0-SNAPSHOT/

      When requesting an jsp using the HTTP method CONNECT, the server sends an empty reply instead of a 405 status. Using the PUT method works as expected.

        1. jsp-error.zip
          2 kB

            rhn-cservice-bbaranow Bartosz Baranowski
            tsstadler Tobias Stadler (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: