4798461
|
GUI does not correctly reflect when `Transmit File' is turned off.
|
4904896
|
I18N search: sort encoding list of Default Encoding on search Administration
GUI.
|
4905412
|
GUI doesn't permit to manage users in the keyfile database.
|
4991338
|
Web Server Administration console does not show all the tabs (in Mozilla
browser).
|
5001819
|
Web Server 6.1: Nova Search Engine sometimes misses to pick up document.
|
5014693
|
Java filters, HTTP compression, and SHTML fail to interoperate.
|
5021077
|
Encountering java.lang.NullPointerException if you
click on OK button without selecting the Directory Server.
|
5025617
|
Web Server's JNDI needs to map resource-env-ref's from sun-web.xml.
|
5042676
|
Request flow problem with Client tag code=302.
|
5056989
|
Enable prefixing of hostname in session ID.
You can enable prefixing hostname in session ID (as in 6.0SPx) for the
web-app by setting the value of the property prefixSessionIDWithHostname under manager-properties to yes, true, or on, in the web-app's sun-web.xml.
In the following example, prefixing host name in session ID is enabled
for the web-app by setting the parameter value to true.
<session-config>
<session-manager>
<manager-properties>
<property name="prefixSessionIDWithHostname" value="true">
</manager-properties>
</session-manager>
</session-config>
|
5057749
|
Web Server 6.1 SP2: Plug-in defined in certmap.conf does
not load.
|
6041356
|
Memory leaks when AdminLanguage and/or DefaultLanguage is specified in magnus.conf.
|
6057426
|
The load balancer plug-in (formerly Resonate plug-in), loadbal.so,
does not work on SPARC Solaris.
Note that the location of the loadbal.so plug-in
is:
server_root/plugins/loadbal.so
|
5065017
|
Servlet session data problem.
|
5048051
|
Create collection fails on Linux with RPM install.
|
5029954
|
Stack size is ignored when ConnQueueSize/RqThrottle is
0.
|
4898077
|
Inconsistent behavior between HttpServerAdmin and
iWS console.
|
5013100
|
Two ports (for example, 2500 and 02500) are added in server.xml as
different ports.
|
5046634
|
2–byte character in HTTP header and plug-in programs.
You can enable response header encoding at the web-app level by setting
the value of the configuration parameter use-responseCT-for-headers to yes, true, or on, in the web-app's sun-web.xml.
In the following example, response header encoding is enabled for the
web-app setting the parameter value to true. A sample sun-web.xml is
as follows:
<sun-web-app>
<parameter-encoding form-hint-field="j_encoding">
<property name="use-responseCT-for-headers" value="true" >
<session-config>
<session-manager>
</session-config>
<jsp-config>
</sun-web-app>
|