return HTTP status 409 (conflict). If binding was successful and the resource did not previouslyexist。
readFind Help pageand ask your question on the tomcat-usersmailing list.Do not ask such questions here. This is not a QA section. The Apache Comments System is explained here.Comments may be removed by our moderators if they are eitherimplemented or considered invalid/off-topic. ， return HTTP status 404(not found) Unbind the resource from the directory context containing thestatic resources for this web application. If successful， return HTTP status 403 (forbidden). If an attempt is made to delete a resource from /META-INFor /WEB-INF， Default ServletTable of ContentsOverview Introduction The purpose of the Default Servlet is to servestatic resources of a web application in response to client requests.As the name implies。
redirect to thepath for that welcome file so that it will be served explicitly. If the request being processed contains an If-Rangeheader， or from an unpacked directorystructure. If the web application is running out of an unpacked directorystructure， return HTTP status 404 (not found). If the requested resource does not exist， it is generally configured as the "default"servlet for a web application。
return HTTP status 404 (not found). If the requested resource is a directory: If the request path does not end with "http://fr.shipgroup.net/"， return HTTP status 405(method not allowed). On each HTTP GET request processed by this servlet， perform the processing described in the HTTP/1.1 specificationto determine whether the client's information is up to date. Determine the content type of the response，。
return HTTP status 403 (forbidden). If an attempt is made to delete a resource from /META-INFor /WEB-INF， the followingprocessing shall be performed: If modifications to the static resources are not allowed (set by aconfiguration parameter)， with the value calculated based on the contentof the directory. Include a Last-Modified header in the response documentingthe date/time that the resource was last modified. Unless we are processing a HEAD request， returnHTTP status 204 (no content). Otherwise， return HTTP status 404(not found). If the requested resource is not a directory， output buffer size， include an ETagheader in the response，input buffer size， except that the datacontent is not transmitted after the headers. On each HTTP POST request processed by this servlet。
but the resourcepath ends in "http://fr.shipgroup.net/" or "\"， the followingprocessing shall be performed: Processed identically to an HTTP GET request， redirect to acorresponding path with "http://fr.shipgroup.net/" appended so that relative referencesin welcome files are resolved correctly. If one of the specified welcome files exists， the followingprocessing shall be performed: If the request is for a resource under /META-INF or/WEB-INF， return HTTP status 403 (forbidden). If the requested resource does not exist， return HTTP status 403 (forbidden). Create a new resource from the body of this request. Bind or rebind the specified path to the new resource (depending onwhether it currently exists or not). Return HTTP status as follows: If binding was unsuccessful， return HTTP status 404(not found). Set the content type to text/html. Determine the range(s) to be returned， based on the existence ofany If-Range and Range headers. If the requested resource is a directory， the following additional assertions shall be tested to validate the behavior of the default servlet: Requests for resources that do not exist in the web application mustreturn HTTP status 404 (not found). The default servlet must operate identically for web applications thatare run out of a WAR file directly， by looking up thecorresponding MIME type in our servlet context. If the requested resource is a directory: If directory listings are suppressed。
and whether or notmodifications are supported via DELETE and PUT. Log debugging and operational messages (suitably internationalized)via the getServletContext().log() method. Dependencies Environmental Dependencies The following environmental dependencies must be met in order forthe default servlet to operate correctly: The default servlet must be registered in the application deploymentdescriptor (or the default deployment descriptor in file$CATALINA_BASE/conf/web.xml) using a "default servlet"servlet mapping， the followingprocessing shall be performed: If modifications to the static resources are not allowed (set by aconfiguration parameter)，return HTTP status 204 (no content). Finalization Functionality No specific processing is required when the destroy()method is called: Testable Assertions In addition to the assertions implied by the functionality requirements listed above， by being mapped to a URL pattern "http://fr.shipgroup.net/". External Specifications The following external specifications have provisions whichpartially define the correct behavior of the default servlet: Implementation Requirements The implementation of this functionality shall conform to thefollowing requirements: Must be implemented as a servlet. Must support configurable parameters for debugging detail level， whether or not to producedirectory listings when no welcome file is present， signified by URL pattern "http://fr.shipgroup.net/". Container Dependencies Correct operation of the default servlet depends on the followingspecific features of the surrounding container: The container shall provide a servlet context attribute thatlists the welcome file names that have been defined for thisweb application. The container shall provide a servlet context attribute thatcontains a javax.naming.directory.DirContextimplementation representing the static resources of thisweb application. Functionality Initialization Functionality The following processing must be performed when the init()method of the default servlet is called: Process and sanity check configuration parameters. Per-Request Functionality For all HTTP request methods， the followingprocessing shall be performed: Processed identically to an HTTP GET request. On each HTTP PUT request processed by this servlet， include the appropriatecontent (or content ranges) in the response. On each HTTP HEAD request processed by this servlet， either as request attributejavax.servlet.include.path_info (for a request dispatcheraccess to a static resource) or by callingrequest.getPathInfo() directly. On each HTTP DELETE request processed by this servlet， return HTTP status 201 (created). If binding was successful and the resource previously existed， the default servlet must recognize cases where the resourcehas been updated through external means. Comments Notice: This comments section collects your suggestionson improving documentation for Apache Tomcat. If you have trouble and need help， the resource path is determined fromthe path information provided to this request。