en.help.task-protocolnew.html Maven / Gradle / Ivy

Go to download




To Create a Protocol



In the navigation tree, expand the Configuration node.


Under the Configuration node, expand the Network Config node.


Under the Network Config node, select the Protocols node.
The Protocols page opens.


On the Protocols page, click New.
The New Protocol page opens.


In the Name field, type a unique name for the protocol.


Select the Security Enabled checkbox to enable security for the protocol.
This option is disabled by default. If you enable security, you can use the SSL tab of the Edit Protocol page to modify the security settings.


Select the Status Enabled checkbox to enable the file cache.
This option is enabled by default.


In the Max Age field, type the maximum age, in seconds, for a valid cache entry.
This parameter controls how long cached information is used after a file has been cached. An entry older than the maximum age is replaced by a new entry for the same file. If your content changes infrequently, increase this value for improved performance.
The optimum maximum age depends on whether existing files are modified regularly. For example, if files are modified four times a day at regular intervals, consider setting the maximum age to 21600 seconds (6 hours). Otherwise, consider setting the maximum age to the longest time for which you are willing to serve the previous version of a file after the file has been modified.
The default value is 30.


In the Max Cache Size field, type the maximum total size (in bytes) of the file cache on disk.
The default value is 10485760.


In the Max File Count field, type the maximum number of files that can be stored in the file cache.
If the value is too big, the server caches little-needed files, which wastes memory. If the value is too small, the benefit of caching is lost. Try different values of this attribute to find the optimal solution for specific applications.
The default value is 1024.


In the Server Name field, type the host name to be used in the URLs the server sends to the client.
This name is the alias name if your server uses an alias. If your server does not use an alias, leave this field blank.
This value affects URLs the server automatically generates; it does not affect the URLs for directories and files stored in the server. If your server uses an alias, the server-name should be the alias name. If a colon and port number are appended, that port is used in URLs the server sends to the client.


From the Default Virtual Server drop-down list, select the virtual server to be associated with this protocol.
Use the Virtual Servers page to define virtual servers.


In the Redirect Port field, type the port value to be used to redirect a request to another port.
The GlassFish Server automatically redirects the request if these two conditions exist:


The network listener that references this protocol is supporting non-SSL requests.


A request is received for which a matching security constraint requires SSL transport.


If a redirect port is not specified, the GlassFish Server uses the port number specified in the original request. By default, no port is specified.


In the Max Connections field, type the maximum number of requests that can be pipelined until the connection is closed by the server.
The Keep-Alive subsystem periodically polls idle connections. The default value is 256.
Set this property to 1 to disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. A value of 0 means requests are always rejected. A value of -1 sets no limit to the number of keep-alive connections.


In the Timeout field, type the maximum time in seconds that a connection can be deemed as idle and kept in the keep-alive state.
A value of 0 or less means that keep-alive connections are kept open indefinitely. The default value is 30 seconds.


Select the Upload Timeout Enabled checkbox to cause the connection for a servlet that reads bytes slowly to be closed after the Connection Upload Timeout limit is reached.
If this option is disabled, servlet connections do not time out. This option is disabled by default.


In the Connection Upload Timeout field, type the timeout for uploads, in milliseconds.
This field is applicable only if the Upload Timeout Disabled checkbox is selected. The default value is 300000 milliseconds.


In the Request Timeout field, type the number of seconds before a request times out.
If the request is not processed before the timeout value is reached, the request is ignored. The default value is 30 seconds.


In the Send Buffer Size field, type the size in bytes of the send buffer.
The default value is 8192 bytes.


In the Header Buffer Length field, type the size in bytes of the buffer used by the request processing threads to read the request data.
The default value is 8192 bytes.


In the Max Post Size field, type the maximum size in bytes of POST actions.
The default value is 2097152 bytes.


In the URI Encoding field, type the name of the character set used to decode the request URIs received.
The value must be a valid IANA character set name. The default value is UTF-8.


In the Version field, type the version of the HTTP protocol used.
The default value is HTTP/1.1.


From the Compression drop-down list, select the use of HTTP/1.1 GZIP compression to save server bandwidth.
Available choices are:

on

Compresses data.

off

Disables compression.

force

Forces data compression in all cases.


The default value is off.


In the Compressible Mime Types field, type a comma-separated list of MIME types for which HTTP compression is used.
The default value is text/html,text/xml,text/plain.


In the Compression Minimum Size field, type the minimum size of a file when compression is applied.
This value must be set if Compression is set to on or force. The default value is 2048 bytes.


In the No-Compression User Agents field, type a comma-separated list of regular expressions matching user-agents of HTTP clients for which compression should not be used.
By default, this value is an empty string.


In the Restricted User Agent field, type a list of restricted user agents on which HTTP compression is applied.
If no user agents are specified, HTTP compression is applied to all user agents. By default, no user agents are specified.


In the Default Response Type field, type a string that specifies the default response type.
The format is a semicolon-delimited string consisting of the content-type, encoding, language, and charset. The default value is text/html; charset=iso-8859-1.


In the Forced Response Type field, type a string that specifies the request type used if no MIME mapping is available that matches the file extension.
The format is a semicolon-delimited string consisting of the content-type, encoding, language, and charset. The default value is text/html; charset=iso-8859-1.


In the Adapter field, type the class name of the static resources adapter.
The default value is com.sun.grizzly.tcp.StaticResourcesAdapter.


Select the Comet Support Enabled checkbox to enable Comet support for the network listener that references this protocol.
By default, this option is disabled. If your servlet or JSP page uses Comet technology, make sure it is initialized when the GlassFish Server starts up by adding the load-on-startup element to your web.xml file. For example:
<servlet>
<servlet-name>CheckIn</servlet-name>
<servlet-class>CheckInServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>


Select the DNS Lookup Enabled checkbox to enable DNS lookup.
This option is disabled by default.


Select the RCM Support Enabled checkbox to enable Resource Configuration Management (RCM).
This option is disabled by default.


Select the Trace Enabled checkbox to enable the TRACE operation.
If this option is disabled, the GlassFish Server is less susceptible to cross-site scripting attacks. This option is enabled by default.


Select the Auth Pass Through Enabled checkbox to indicate that the network listener that uses this protocol receives traffic from an SSL-terminating proxy server.
This option is disabled by default.


Select the Chunking Enabled checkbox to enable HTTP response chunking.
This option is enabled by default.


Select the XPowered By Enabled checkbox to tell the GlassFish Server to use X-Powered-By headers according to the Java Servlet 3.0 and Java Server Pages 2.0 specifications.
This option is enabled by default.



Next Steps
After you create a protocol, you can create a network listener that uses the protocol.

See Also


To Create a Network Listener


To Edit a Network Listener


To Delete a Network Listener


To Edit a Protocol


To Edit SSL Settings for a Protocol


To Edit HTTP Settings for a Protocol


To Edit File Cache Settings for a Protocol


To Delete a Protocol


To Create a Transport


To Edit a Transport


To Delete a Transport




Copyright © 2005, 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices