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

No reload required when add mime-mapping to servlet-container

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 10.0.0.Alpha4
    • 10.0.0.Alpha3
    • Web (Undertow)
    • None
    • Hide

      When server is running from CLI:

      Deploy some war (example attached) and set mime-mapping to myext file extension:

      deploy simple-web.war
./servlet-container=default/mime-mapping=myext:add(value="text/richtext")

      then try some request on address

      localhost:8080/simple-web/welcome.myext

      In appropriate response the header Content-Type does not contain expectet value "text/richtext". After server reload is performed then Content-Type header has expected value.

      Show
      When server is running from CLI: Deploy some war (example attached) and set mime-mapping to myext file extension: deploy simple-web.war ./servlet-container= default /mime-mapping=myext:add(value= "text/richtext" ) then try some request on address localhost:8080/simple-web/welcome.myext In appropriate response the header Content-Type does not contain expectet value "text/richtext". After server reload is performed then Content-Type header has expected value.

      When mime-mapping is added to servlet container then no reload of server is required, although change takes effect after server restart is performed.

      Expected behaivour is either that change takes effect immediatelly after configuration is changed or that server reload is required in response message and result of the operation.

        1. simple-web.war
          0.6 kB

            sdouglas1@redhat.com Stuart Douglas
            jstourac@redhat.com Jan Stourac
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: