Title: Configure the Web Subsystem Describe the issue: Having this content in tabular format makes it difficult to read and doesn't allow for content wrapping to suit other layouts (e.g. PDF). Suggestions for improvement: The tables in this section need to be removed and their content reformatted so that it is: more easily read and able to be restyled (e.g. lines wrapped as need to fit other published formats).
There isn't any Servlet/HTTP Subsystem in EAP. Note that Web Console has mod_cluster and Web Services shown under Web subsystem which is incorrect. Those are separate subsystems in EAP.
Global Configuration Options * Default for native attribute is 'true' not 'false' JSP Configuration Options * Check Interval - what 0 as default value means? 0 means that checks are disabled, see [1] * Keep Generated - the name of CLI attribute is keep-generated * X Powered By - I would change "advertised in x-powered-by" to "advertised using x-powered-by HTTP header" * There still are not all options described, see /subsystem=web/configuration=jsp-configuration:read-resource-description [1] https://docs.jboss.org/jbossweb/7.0.x/config/jsp.html
Connector Options * Protocol - HTTP vs AJP are possible protocols that is correct, here should be also added different possible implementations of those protocols, e.g. for HTTP there are JIO, NIO2 and APR protocols, the definition can be done either by defining only the API (HTTP/1.0 vs HTTP/1.1, ...) and server decides which implementation to use or by FQCN (e.g org.apache.coyote.http11.Http11Protocol for JIO or org.apache.coyote.http11.Http11NioProtocol for NIO2 or org.apache.coyote.http11.Http11AprProtocol for APR, note, APR is available only with natives enabled)
*** Bug 1134162 has been marked as a duplicate of this bug. ***
I have checked it with docs revision 6.4.0-34 and these are my findings: Missing default value for "Error on Use Bean Invalid Class Attribute" (default value is false) Next there is typo in FQCN for NIO2, where is missing org.: is apache.coyote.http11.Http11NioProtocol => should be org.apache.coyote.http11.Http11NioProtocol - this is being resolved as part of https://bugzilla.redhat.com/show_bug.cgi?id=1121137#c2 Next regarding APR: there is no need to install Webserver Connectors Native package (that package contains modules for httpd and load balancing). You need to install Native Components package (which contains the APR, see https://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Installation_Guide/index.html#Download_and_Install_Native_Components_and_Native_Utilities). Regarding Virtual Servers Options two suggestions: alias - "A list of hostnames which must match this virtual server" - wouldn't it be better "A list of hostnames supported by this virtual server" as this option means that if you access one of the hostnames in the alias, then options specific for that virtual server shall be used? Default module - instead of "must be deployed" wouldn't it be better "will be deployed" ?
Checked with docs revision 6.4.0-35. There was added example of CLI command showing how to read connector description [1]. This example is for standalone containing part of command line. This is inconsistent to the way other CLI examples are constructed e.g. Example 15.2. Create a New Connector contains command for server in domain mode without command line prompt prefix [2]. I believe this should be consistent. MaxTime description typo: there should be singular in word request and not plural ("Max time spent to process a requests." => "Max time spent to process a request.") processingTime description typo: should be "In milliseconds" and not "Im milli-seconds" [1] [standalone@localhost:9999 /] /subsystem=web/connector=http:read-resource-description [2] /profile=full-ha/subsystem=web/connector=ajp/:add(socket-binding=ajp,scheme=http,protocol=AJP/1.3,secure=false,name=ajp,max-post-size=2097152,enabled=true,enable-lookups=false,redirect-port=8433,max-save-post-size=4096)
Additionally changing Connector options names to those in CLI doesn't correspond to the way options for other parts are written (e.g. JSP configuration options).
access-log wasn't removed, It is child of the virtual server (one of configuration childs). It can be created via CLI command /subsystem=web/virtual-server=default-host/configuration=access-log:add() It is similar for sso, which is also one of virtual server configuration childs /subsystem=web/virtual-server=default-host/configuration=sso:add
*** Bug 1016107 has been marked as a duplicate of this bug. ***
*** Bug 1016080 has been marked as a duplicate of this bug. ***
I just checked trying to define HTTP protocol using API name "HTTP/1.0" and found out it is not possible, sorry if I confused you by Comment 5. On the contrary, it is possible to define the protocol as "http", which behaves the same as defining it to "HTTP/1.1".
Sentence just before describing connector options: "AJP and HTTP connectors use mod_cluster, mod_jk, mod_proxy, ISAPI connector, and NSAPI connector for load balancing and HA clustering. " shouldn't be there as AJP and HTTP connectors in Web subsystem have nothing to do with load balancers as are mod_cluster, mod_jk, mod_proxy, ... The connectors just implement the specific protocol, which can be used during communication between load balancer and the server (worker).
Additionally there is missing: default value for Maximum Save Post Size, which is 4096. description of access-log attributes description of SSO attributes
Verification was done against Administration and Configuration Guide, revision 6.4.0-37
Checked with docs Revision 6.4.0-39. There is still few more improvement which should be incorporated there. The description of "resolve-hosts" attribute should contain info that it is also necessary to enable-lookups on the connector for "resolve-hosts=true" option to actually take any effect. The description of rewrite attributes * description of "flags" attribute is missing. * description of "condition" - there is no condition attribute, there is condition child resource of rewrite, which can be defined as child of the rewrite and is used to limit the rewrite rule only to cases with matching conditions when the rewrite should occur. Description of SSO attributes is missing info about default values, which is in case of http-only true.
The title looks weird... "Servlet/HTTP Configuration" why? You should put the metrics separated from the attributes. (like Bytes Received).
EAP7.0 uses undertow so the web subsystem docs have to be completely rewritten.
I agree with Jean-Frederic, having the metrics (runtime) attributes separately would make more sense. Rewrite resource and its flag attribute description is not correct. In case of Web subsystem configuration, the flags are provided without the brackets. Regarding SSO * the sso configuration is either added or not, in default it is not added => no SSO. * regarding comment 43 and its SSO part it mentions mainly missing specified default value for http-only attribute of the SSO configuration. So the default should be added to the http-only attribute description.
Note, which attributes are metrics can be easily found out from CLI's ":read-resource-description operation". Metrics attributes have defined "access-type" as "metric".
Work is ongoing to rewrite this information for 7.0. Work tracked in JIRA with the larger EAP project so I'm closing this BZ that was opened about a year ago.