schemas.wsdl.http-conf.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of cxf-bundle-minimal Show documentation
Show all versions of cxf-bundle-minimal Show documentation
Apache CXF Minimal Bundle Jar
Properties used for configuring a server-side HTTP prort
Receive timeout in milliseconds, 0 is infinite
When set to false, exceptions will be thrown when an error is encountered
receiving a request from the client. When set to true these errors will
be suppressed. The default is false.
When set to false, exceptions will be thrown when an error is encountered
sending a reply from to client. When set to true these errors will be
suppressed. The default is false.
When set to true, the request socket will remain open after the reply is
sent to the client, if the client has requested keep-alive and is using
at least version 1.1 of HTTP. If set to false, the socket will be closed
after each reply is sent, even if the client requests the server to keep
the connection alive. Keep-Alive improves performance for the client
requesting such behavior, but can limit overall scalability of the server
for handling many clients. The Default is true.
If KeepAlive connections are turned on, this allows sending additional
parameters back to the client via the Keep-Alive header. Common
parameters are timeout and max to specify how long the client should
hold open the connection and how many connections to hold open. Different
clients may have different defaults. For Java HTTPUrlConnection, the
defaults would be timeout=5, max=5
Example: timeout=60, max=5;
A URL to which clients are redirected (if the ReplyCode and ReplyDescription
are not set, ReplyCode will be set to 302, and ReplyDescription will be set
to 'Object Moved').
Most commonly used to specify no-cache, however the standard supports a
dozen or so caching related directives for responses.
Specifies the URL representing the resource used to satisfy the request(e.g., to inform that default.htm document was used.)
Specifies the MIME type used for responses. The default is set by the binding.
Specifies any additional encoding applied to the response. Values are specified using IANA labels.
Specifies an optional value for the HTTP ServerType property.
Properties used to configure a client-side HTTP port
Specifies the amount of time, in milliseconds, that the consumer will attempt to establish a connection before it times out. 0 is infinite.
Specifies the amount of time, in milliseconds, that the consumer will wait for a response before it times out. 0 is infinite.
Specifies if the consumer will automatically follow a server issued redirection.
(name is not part of standard)
Specifies the maximum amount of retransmits that are allowed for redirects. Retransmits for
authorization is included in the retransmit count. Each redirect may cause another
retransmit for a UNAUTHORIZED response code, ie. 401.
Any negative number indicates unlimited retransmits,
although, loop protection is provided.
The default is unlimited.
(name is not part of standard)
If true, the client is free to use chunking streams if it wants, but it is not
required to use chunking streams. If false, the client
must use regular, non-chunked requests in all cases.
If AllowChunking is true, this sets the threshold at which messages start
getting chunked. Messages under this limit do not get chunked.
Specifies the MIME types the client is prepared to handle (e.g., HTML, JPEG, GIF, etc.)
Specifies the language the client desires (e.g., English, French, etc.)
Specifies the encoding the client is prepared to handle (e.g., gzip)
Specifies the content type of the stream being sent in a post request.
(this should be text/xml for web services, or can be set to
application/x-www-form-urlencoded if the client is sending form data).
Specifies the Internet host and port number of the resource on which the request is being invoked.
This is sent by default based upon the URL. Certain DNS scenarios or
application designs may request you to set this, but typically it is
not required.
The connection disposition. If close the connection to the server is closed
after each request/response dialog. If Keep-Alive the client requests the server
to keep the connection open, and if the server honors the keep alive request,
the connection is reused. Many servers and proxies do not honor keep-alive requests.
Most commonly used to specify no-cache, however the standard supports a
dozen or so caching related directives for requests
Specifies a cookie to send to the server. Some stateful session designs will use cookies to identify a session.
If the cookie is static, you can supply it here. If it is dynamic,
it will need to be set by the server on first access, and can be handled
automatically by the runtime.
aka User-Agent
Specifies the type of browser is sending the request. This is usually only
needed when sites have HTML customized to Netscape vs IE, etc, but can
also be used to optimize for different SOAP stacks.
Specifies the URL that referred us to this URL. This is
sent automatically with auto redirect.
May allow the server to optimize processing based upon
previous task flow. However, typically not used in
web services applications.
Specifies the URL of a decoupled endpoint for the receipt of responses over a separate provider->consumer connection.
Specifies the address of proxy server if one is used.
Specifies the port number used by the proxy server.
Specifies the list of hostnames that will not use the proxy configuration.
Examples of value:
* "localhost" -> A single hostname
* "localhost|www.google.com" -> 2 hostnames that will not use the proxy configuration
* "localhost|www.google.*|*.apache.org" -> It's also possible to use a pattern-like value
Specifies the type of the proxy server. Can be either HTTP or SOCKS.