WebtoB 5 Fix#3

This chapter describes the changes and additions in functionality and bug patches in WebtoB 5 Fix#3.

1. New Functions

1.1. HTTP/2 Support

  • Newly supports HTTP/2 connections and requests.

    Set HTTP2Flag = Y in the NODE section, and configure SSLFlag in the NODE or VHOST section because it is supported only when using SSL/TLS protocol.

    *NODE
webtob      WebtoBDir = "$WEBTOBDIR",
            SSLFlag = Y,
            HTTP2Flag = Y,
                    :
                    :

2. Added Functions

2.1. More Actions in the HEADERS Section

  • Added the following Action functions in the HEADERS section.

    * HEADERS
header1         Action="AddIfAbsentRequest",
                FieldName="Test_Header",
                FieldValue="test"

header2         Action="AddIfAbsentResponse",
                FieldName="Test_Header",
                FieldValue="test"

header3         Action="AppendResponse",
                FieldName="Test_Header",
                FieldValue="AppendResponse"

header4         Action="EchoResponse",
                FieldName="Test_Header"
    Action Description

    AddIfAbsentRequest, AddIfAbsentResponse

    Can be added only when no fields have been configured. For Apache, specific conditions can be set with additional settings such as SetEnvIf.

    AppendResponse

    When there exists a pre-configured field, an additional value can be set with a comma (,).

    EchoResponse

    When a pre-configured field exists in the Request header, the same value can be added.

    For more information about the usage, refer to HEADERS Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-233552

2.2. XFF Header Support for WJP

  • Added a function that enables the transmission of the XFF (X-Forwarded-For) header from the client’s Request header to JEUS as a remote IP.

  • Related Issue: IMS-208907

2.3. Header in Reverse Proxy

  • Added support for X-Forwarded-Proto and X-Forwarded-Port headers in Reverse Proxy.

  • Related Issue: IMS-213003

2.4. Error Log Format Setting in the LOGGING Section

  • Added a function for formatting error logs in the LOGGING section, using the same approach for access logs.

    *LOGGING
error_log       Format = "ERROR", # "%h %l %u %t \"%r\" %s %b",
                Filename = "log/archives/error_%Y%%M%%D%.log",
                Option = "sync",
                    :
                    :

    Be careful not to confuse error logs with access logs, as they use the same formatting approaches. For more information about its usage, refer to LOGGING Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-213098, IMS-211162

2.5. RotateByFileSize in the LOGLEVEL Section

  • Added the RotateByFileSize function in the LOGLEVEL section, which regenerates log files based on the file size.

    For more information about its usage, refer to LOGLEVEL Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-233595

2.6. -rf Option for the loglevel Command

  • Added the -rf (RotateByFileSize) option for the loglevel command in wsadmin, and changed the existing -r option to -rs (RotateBySeconds).

    *LOGLEVEL
.hth            Level="Trace",
                RotateBySeconds = 100,
                RotateByFileSize = 10000,
                options ="dsW",
                    :
                    :
    $$1 tmaxsoft (wsadm) [2020-08-11T17:26:46]: cfg -ll
    LOGLEVEL: Logger = .hth,
         Level = TRACE,
         Options = dsW,
         RotateBySeconds = 100,
         RotateByFileSize = 10000

$$1 tmaxsoft (wsadm) [2020-08-03T01:40:06]: ll
Usage: ll loggername -l level | -o options | -rs rotatebyseconds | -rf rotatebyfilesize
            loggername : name of the logger (e.g. .hth)
            level : TRACE|DEBUG|INFO|WARN|FATAL
            options : [-]dcR,dcW,dsR,dsW
                      '-' turns off the specified options
            rotatebyseconds : trace log files separately by time (e.g. 500)
            rotatebyfilesize : trace log files separately by file size (e.g. 100000000)

    For more information about the usage, refer to ll in WebtoB Administrator’s Guide.

  • Related Issue: IMS-233595

2.7. SessionIdUrlKey in the SERVER Section

  • Added the SessionIdUrlKey function in the SERVER section, which maintains sessions in browsers that block cookies.

    *SERVER
MyGroup     SvgName = jsvg,
            MinProc = 10,
            MaxProc = 20,
            SessionIdUrlKey = "jsessionid",
                    :
                    :

  • If both SessionIdCookieKey and SessionIdUrlKey are configured, SessionIdCookieKey takes precedence.

    For more information about the usage, refer to SERVER Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-204793

2.8. FA Scheduling for Worker Threads

  • Added the FA (First Available) scheduling mode to address a situation where there are blocked worker threads.

  • You can set the schedule setting to FA or RR in the HTH_THREAD section. (Default value: FA)

    *HTH_THREAD
hth_worker      SendfileThreads = 10,
                SendfileThreshold=32768,
                Schedule = FA,
                    :
                    :

    The following describes each setting value.

    Value Description

    RR

    Round Robin mode. Incoming requests are allocated to all worker threads sequentially.

    FA

    First Assign mode. Incoming requests are primarily allocated to the least loaded worker thread.

    For more information about the usage, refer to HTH_THREAD Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-212463

2.9. Supplementary Code for Queued Requests After Timeout

  • Added supplementary code for preventing HTH core issues and processing subsequent requests in the queue after a timeout occurred while the client’s request was being sent to JEUS.

  • When the added supplementary code is running, the HTH0529 message is printed in the syslog.

  • Related Issue: IMS-222345

2.10. task_type for the 'st -t' Command in wsadmin

  • Added task_type for the 'st -t' command of wsadmin, to print the type of a task that is being processed by the worker thread.

  • The task type is displayed only when the worker thread is in the RUN state, (otherwise NONE), and even though the status is RUN, the task type may be marked as NONE.

    $$74 tmaxsoft (wsadm) [2020-07-29T11:21:54]:  st -t

HTH 0: RDY
-------------------------------------------------------------------------------------
no  thread_id     status   elapsed        atasks        ptasks    qtasks    task_type
-------------------------------------------------------------------------------------
 0   ACCESSLOG      RDY          0        453115        453115         0         NONE
 1   WORKER001      RUN          0        326226        326225         1     SSLWRITE
 2   WORKER002      RUN          0        167882        167881         1      SSLREAD
 3   WORKER003      RUN          0        134442        134441         1      SSLREAD
 4   WORKER004      RDY          0        106250        106250         0      SSLREAD
 5   WORKER005      RDY          0         81404         81404         0         NONE
 6   WORKER006      RDY          0         58007         58007         0         NONE
 7   WORKER007      RDY          0         37496         37496         0         NONE
 8   WORKER008      RDY          1         20338         20338         0         NONE
 9   WORKER009      RDY          1         10957         10957         0         NONE
10   WORKER010      RDY          1          5671          5671         0         NONE

    For more information about the usage, refer to stat (st) in WebtoB Administrator’s Guide.

  • Related Issue: IMS-120109

2.11. Displaying Remote IP in Messages When Connections for JSV are Insufficient

  • Added a function to print the client IP (remote IP) in the system logs ([HTH-00063] and [HTH-00292]) when there are insufficient connections (SPR) for JSV.

  • Related Issue: IMS-223842

2.12. String Formatting for Logging in FieldValue in the HEADERS Section

  • Added support for string formatting for logging in FieldValue in the HEADERS section.

  • Supports the escape character '%' for log formatting.

2.13. IncludeSslDump Option in the LOGLEVEL Section

  • Added the IncludeSslDump option in the LOGLEVEL section, which includes SSL Dump in trace logs. (Default value: N)

2.14. IPGroup in the ACCESS Section

  • Added IPGroup in the ACCESS section to facilitate configuration for grouping Allow/Deny IPs.

  • The IP group names can be used in the Allow or Deny setting in the ACCESS section.

    *IPGroup
ipgroup1        IP = "localhost, 192.168.13.49"
ipgroup2        IP = "localhost, 192.168.13.49, 192.168.13.50"

*ACCESS
access_allow    Order = "allow,deny",
                Allow = "ipgroup1"
access_deny     Order = "deny,allow",
                Deny  = "ipgroup2"

    For more information about the usage, refer to ACCESS Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-201979

2.15. Individual Encoding for VHOST

  • Added a function to configure encoding individually for each vhost.

    *VHOST
vhost1              :
                CheckURL = Y, # default : N
                CheckURLFrom = "euc-kr", # default: utf-8
                CheckURLTo = "utf-8",
                CheckUrlJsvExcept = Y, # default : N
                    :
                    :

    The following describes each setting value.

    Value Description

    CheckURL

    Indicates whether to convert the charset of the HTTP Request URL path. If set to Y, CheckURLFrom and CheckURLTo need to be configured.

    CheckURLFrom

    Specifies the charset used by the HTTP Request URL path.

    CheckURLTo

    Specifies the charset used by the server.

    CheckUrlJsvExcept

    Indicates whether to apply the CheckURL setting for a request that will be forwarded to JEUS. If set to Y, the URI will not be converted when the request is sent to JEUS.

    For more information about the usage, refer to VHOST Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-201972

2.16. MultiStatus in the ERRORDOCUMENT Section

  • Added MultiStatus to configure multiple HTTP status codes for the same URL.

  • The specified statuses will be applied in the order where each status has been specified.

    *ERRORDOCUMENT
errordoc1       MultiStatus = "403,404,413,414,500,503",
                Url = "/error.html",
                    :
                    :

    For more information about the usage, refer to ERRORDOCUMENT Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-196685

2.17. LOGHANDLER Settings

  • Added a function to leave WebtoB access logs in a user-specified remote server. The remote server’s address, path of the log files, and a connection timeout can be configured.

  • The LOGHANDLER name can be used for the LogHadler setting in the LOGGING section.

    *LOGHANDLER
lh1             ServerAddress = "remote.server.com:8080",
                ConnectTimeout = 3,
                ReconnectTime = 10,
                Timeout = 60,
                Resource = "webtob/accesslog",
                Protocol = "HTTP",
                    :
                    :

    The following describes each setting value.

    Item Description

    LOGHANDLER setion name

    Name of the LOGHANDLER section. (e.g. lh1)

    ServerAddress

    Address of the remote server in which access logs will be saved.

    ConnectTimeout

    Time period during which a request for connection to the remote server waits for the connection.

    ReconnectTime

    Time period during which a request waits for reconnection to the remote server after a connection attempt has failed.

    Timeout

    Time period during which the connection to the remote server remains idle without receiving any requests for storing access logs. After the timeout, the remote server connection will be closed.

    Resource

    Path of the location in which access logs will be stored in the remote server.

    Protocol

    Protocol to use for sending access log requests to the remote server.

    For more information about the usage, refer to LOG_HANDLER Section and LOGGING Section in WebtoB Administrator’s Guide.

2.18. Command logsearch to Look for Log Files Contents

  • Added a function to search for a specific string in a log file specified by using the webadmin command.

    $$1 webtob (wsadm)
[2020-07-29T14:58:35]: logsearch successfully system.log_07292020
[2020-07-29T10:44:16] [HTH(22378)] [I] [HTH-00074] Successfully connected and
registered to HTL. HTH is ready to receive client connections.
[2020-07-29T10:44:16] [HTL(22377)] [I] [HTL-00021] Successfully registered HTH.
Start listening for this HTH. index=0, fd=6
[2020-07-29T14:57:29] [HTH(4901)] [I] [HTH-00074] Successfully connected and
registered to HTL. HTH is ready to receive client connections.
[2020-07-29T14:57:29] [HTL(4900)] [I] [HTL-00021] Successfully registered HTH. Start
listening for this HTH. index=0, fd=6

    For more information about the usage, refer to logsearch in WebtoB Administrator’s Guide.

  • Related Issue: IMS-186536

2.19. Option to Raise an Error for Invalid HTTP Request header

  • Added an option to raise an error when an HTTP request header is invalid. It is possible to either ignore the invalid header or handle it as an error.

  • An HTTP request header consists of a name and value pair, separated by a colon ("name:value"). This option determines whether to ignore a header that lacks a colon and proceed to the next header.

    *NODE
webtob              :
                IgnoreMissingColonErr = Y,
                    :
    Item Description

    IgnoreMissingColonErr

    The following describes the setting values.

    • Y: Ignores an invalid header.

    • N: Sends a "400 Bad Request" response.

    For more information about the usage, refer to NODE Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-178412

2.20. Headers Settings Added in Reverse Proxy

  • Added the Headers setting in REVERSE_PROXY_GROUP and REVERSE_PROXY, to support headers for Reverse Proxy.

  • The configuration and behaviors are the same as the Headers settings in the SERVER and SVRGROUP sections.

    *REVERSE_PROXY_GROUP
rproxygroup1        :
                Headers = "header1, header2"

*REVERSE_PROXY
rproxy1             :
                Headers = "header1, header2"

    For more information about the usage, refer to REVERSE_PROXY_GROUP Section and REVERSE_PROXY Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-178383

2.21. LBSvgName Added in the URI Section for Load Balancing

  • Added a function to distribute load between servers based on the SvrGroup settings.

  • The SVRGROUP setting specified by LBSvgName must contain the LBServers or LBBackup option.

    *URI
uri1            Uri = "/jsvtest/",
                Svrtype = JSV,
                LBSvgName = jsvg

*SVRGROUP
jsvg            SvrType = JSV,
                LBServers  = "MyGroup",
                LBBackup   = "MyGroup2"

*SERVER
MyGroup         SVGNAME = jsvg
MyGroup2        SVGNAME = jsvg

    For more information about the usage, refer to SVRGROUP Section and SERVER Section in WebtoB Administrator’s Guide.

  • Related Issue: IMS-173652

3. Updated Functions

3.1. WBSSL Version Upgrade

  • Upgraded from WBSSL 3.1_1.0.2s to WBSSL 1.1.1d.

  • Supports the TLS v1.3 protocol.

  • No longer supports versions that are less than SSL v3.

    $>wbssl version
WBSSL 1.1.1d  10 Sep 2019

  • Starting from the current version, OpenSSL version numbers are used instead of unique version numbers specific to WBSSL.

3.2. -r Option of the loglevel Command Changed to -rs

  • Changed the existing -r option to -rs (RotateBySeconds), to add the -rf (RotateByFileSize) functionality to the loglevel command of wsadmin.

    $> wsadmin
$$3 tmaxsoft (wsadm) [2020-08-11T15:42:18]: ll
Usage: ll loggername -l level | -o options | -rs rotatebyseconds | -rf rotatebyfilesize
loggername : name of the logger (e.g. .hth)
level : TRACE|DEBUG|INFO|WARN|FATAL
options : [-]dcR,dcW,dsR,dsW
          '-' turns off the specified options
rotatebyseconds : trace log files separately by time (e.g. 500)
rotatebyfilesize : trace log files separately by file size (e.g. 100000000)

    For more information about the usage, refer to ll in WebtoB Administrator’s Guide.

  • Related Issue: IMS-233595

3.3. Increased Maximum Value for RegExp String

  • Changed the maximum string size from [256] to [512] for RegExp in the SVRGROUP, REVERSE_PROXY_GROUP, REVERSE_PROXY, HEADERS, and EXT sections.

  • Related Issue: IMS-217612

3.4. Default Value of SendfileThreshold Changed in the HTH_THREAD Section

3.5. Default Value of InitialConnectionTimeout Changed in the NODE Section

  • Changed the default value of the InitialConnectionTimeout setting in the NODE section from 0 to 10.

3.6. Log Level Changes

  • Modified log levels

    • Changed the log levels for HTH0374 and HTH0295 from FATAL to DEBUG.

    • Changed the log levels for HTH0113 and HTH0099 from INFO to DEBUG.

    • Changed the log levels for HTH0295 and HTH0374 from FATAL to DEBUG.

    • Changed the log level for HTH0094 from DEBUG to WARN.

    • Changed the log level for HTH5037 to DEBUG.

  • Related Issue: IMS-233567, IMS-222345, IMS-197843, IMS-193693

3.7. No Cache for Responses to Requests Ending with a Directory URI

  • Responses to any requests ending with a directory URI are no longer cached.

  • Related Issue: IMS-239793

3.8. Behaviors Changed When the Request and Errordoc Have the Same URL

  • Changed the behaviors of methods other than GET and POST to align with the behaviors of GET, in order to prevent infinite loops if the request URL matches the errordoc’s URL when using other methods than GET and POST.

  • Related Issue: IMS-197432

3.9. Exception Handling for Managing Client Connections During SSL Processing

  • Fixed the problem where waiting occurred until the timeout without recognizing the client has been disconnected during SSL processing.

  • Related Issue: IMS-197455

3.10. Supplementary Code for Unrequested Responses from JSV

  • Added supplementary code to check for any responses that are not intended for WebtoB’s requests towards JEUS, discard those responses and disconnect the corresponding JSV connections.

  • Added HTH0499 as a related message.

  • Related Issue: IMS-170761

4. Bug Patches

4.1. Fix for Intermittently failed JSV Compression

  • Fixed the issue where JSV compression intermittently failed.

  • Related Issue: IMS-204873

4.2. Fix for No CRLF When Processing Chunked Requests Larger than Ring buffer

  • Fixed the issue where it was unable to find the CRLF when processing chunked requests that were larger than the ring buffer.

  • Related Issue: IMS-207302

4.3. Fix for Incorrect '%b' in Access Log for Chunked JSV Response

  • Fixed the issue where '%b' (the response size) was incorrectly calculated and printed in the access log for a JSV response containing the header Transfer-Encoding: chunked.

  • Related Issue: IMS-233567

4.4. Fix for HTH Core Bug When Using AddResponse in HEADERS

  • Fixed the core bug issue which occurred when adding a large header by using the AddResponse setting in the HEADERS configuration.

  • Related Issue: IMS-233568

4.5. Fix for Options Setting Bugs in NODE and VHOST

  • Fixed the issue where -PYTHON and -FILTER were unavailable in the Options setting in the NODE and VHOST sections.

  • Related Issue: IMS-210035

4.6. Fix for Core Bug from wscfl When Configuring LBBackup in SVRGROUP

  • Fixed the core bug issue that occurred when running wscfl for configuring the LBBackup setting in the SVRGROUP section.

  • Related Issue: IMS-213425

4.7. Fix for Integer Overflow During cachelist Processing

  • Fixed the issue where, during processing of the cachelist command, the total content length of the cache list exceeded the maximum int value, resulting in an overflow to a negative number.

  • Related Issue: IMS-221376

4.8. Fix for Incorrect 'conns' Printing During Execution of 'restat' in Reverse Proxy

  • Fixed the issue where the 'st -rpg' command, used to view information, incorrectly printed the conns item (number of connections) when initializing statistics with the 'restat' command in a Reverse Proxy environment.

  • Related Issue: IMS-181798

4.9. Fix for No SHMS Restart for JSV at HTH Startup

  • Fixed the issue where duplicate or repeated HTH connections were displayed when restarting HTH, because SHMS had not been initialized for JSV at the startup of HTH.

  • Related Issue: IMS-223842

4.10. Fix for Memory Leak When Sending 100-continue Response

  • Fixed the issue of memory leaks that occurred when using "Expect: 100-continue" in the request header.

  • Related Issue: IMS-223192

4.11. Fix for WSM Conflict During WebtoB Shutdown

  • Fixed the issue of WSM conflicts that prevented WebtoB from successfully shutting down.

  • Related Issue: IMS-231536

4.12. Fix for Incorrect Status Code Response to Invalid DIGEST Request

  • Fixed the issue where the status code 400 was inadvertently sent instead of "401 Unauthorized" in response to an HTTP BASIC/DIGEST authentication request with an invalid authorization information.

  • Related Issue: IMS-232848

4.13. Fix for HTH Core Bug When Using the unsetResponse Header

  • Fixed the issue of HTH core that occurred when using the unsetResponse header.

  • Related Issue: IMS-234960

4.14. Fix for HTH Core Bug When Executing the hthmem Command in SunOS SPARC

  • Fixed the issue of HTH core that occurred when executing the hthmem command in SunOS SPARC.

  • Related Issue: IMS-201358, IMS-201303

4.15. Fix for HTH Core Bug During Buffer Reallocation for Compression and Header AddResponse

  • Fixed the issue of HTH core that occurred during buffer reallocation to accommodate larger data, which was added as a result of using AddResponse in the Headers section.

  • Related Issue: IMS-238001

4.16. Fix for HTH Core Bug During WebDAV PROPFIND Method Processing

  • Fixed the issue of HTH core that occurred due to a response body exceeding 8 KB during the processing of the WebDAV PROPFIND method.

  • Related Issue: IMS-238863

4.17. Fix for Incorrect cfl Line Number Printing in CFL-05010 and CFL-05011

  • Fixed the issue where, when setting an option not supported by Windows, executing 'wscfl' would print the option’s setting value in CFL-05010 and CFL-05011.

  • Related Settings: HTH_THREAD.SendfileThreads, SendfileThreshold, AccessLogThread

  • Related Issue: IMS-239953

4.18. Fix for Core Bug When Calling Directory URI with ServiceOrder 'EXT, URI'

  • Fixed the issue where calling a directory URI with the ServiceOrder set as 'EXT,URI' resulted in the request being added to the cache, causing a core bug.

  • Modified to ensure that responses to requests ending with a directory URI are not cached, irrespective of the ServiceOrder setting.

  • Related Issue: IMS-239793

4.19. Fix for Timeout Error Due To a JSV Message Exceeding the Setting Value

  • Fixed the issue where an infinite loop and timeout error occurred if the size of a message sent from JEUS to WebtoB via JSV exceeded the FlowControl buffer setting in WebtoB.

  • Related Issue: IMS-203845

4.20. Fix for HTH Core Bug Due To CacheMaxCompressSize

  • Fixed the issue where an HTH core bug occurred when setting CacheMaxCompressSize.

  • Related Issue: IMS-203032

4.21. Fix for HTH Core Bug Due To PROXY_SSL

  • Fixed the issue where, if PROXY_SSL was set, terminating the connection before the client received the response resulted in an HTH core bug.

  • Related Issue: IMS-203281

4.22. Fix for HTH Core Bug Due To Using PROXY_SSL With PersistentConnection

  • Fixed the issue where an HTH core bug occurred when using PROXY_SSL and PersistentConnection at the same time in ReverseProxy.

  • Related Issue: IMS-176628

4.23. Fix for Error Occurring When Sending Messages in Reverse Proxy with PROXY_SSL

  • Fixed the issue where, when sending a chunked message in Reverse Proxy with the PROXY_SSL setting, an internal event processing issue occurred, resulting in the generation of a 400 or 404 error.

  • Related Issue: IMS-187018

4.24. Fix for No Output Issue When Executing SSL Write for Responses

  • Fixed the issue where certain static files were not processed due to an incorrect determination that the client had been disconnected during SSL writing for a response that had been processed in MyWebServer HTMLS.

  • Related Issue: IMS-202614

4.25. Fix for SSL Requests Not Being Processed

  • Fixed the issue where certain SSL requests were not processed by modifying the errorno (error numbers) processing mechanism for SSL errors processing.

  • Related Issue: IMS-197920

4.26. Fix for HTH Core Bug During JEUS Shutdown While Using WJPv2

  • Fixed the issue where an HTH core bug occurred due to failed message processing during the shutdown of JEUS while using WJPv2.

  • Related Issue: IMS-197843

4.27. Fix for HTH Core Bug During Error Logging for Large Chunked Requests

  • Fixed the issue where an HTH core bug issue occurred during the error logging for a karge chucked request.

  • Related Issue: IMS-185884

4.28. Fix for HTH Core Bug During Large Files Caching Through FlowControl Buffer

  • Modified to cache only responses, including the header, that exceed the FlowControl buffer size.

  • Modified to limit the maximum setting value for CacheMaxFileSize to a value smaller than the FlowControl buffer size.

  • Related Issue: IMS-190625

4.29. Fix for Core Bug While Sending Compressed JSV Responses To Client Via SSL

  • Fixed the issue where a core bug occurred when attempting to send a compressed JSV response to the client via SSL. This was caused by the response size and compressed contents being too large to be sent in a single attempt.

  • Related Issue: IMS-188265

4.30. Fix for Erroneous Disconnection Without Sending Response Messages During Normal Shutdown of JEUS

  • Fixed the issue where, during a normal shutdown of JEUS while using WJPv2, an erroneous disconnection occurred without completing the requests that were being processed.

  • Related Issue: IMS-187653

4.31. Fix for No initialization of TCPGW information When Executing 'restat -a'

  • Fixed the issue where the 'restat -a' command in wsadmin was unable to initialize the information printed with 'st -tcpgw'.

  • Related Issue: IMS-176845

4.32. Fix for HTH Core Bug When RequestLevelPing Is Used with Client Connected Via SSL

  • Fixed the core bug that occurred when the RequestLevelPing feature was set to Y while the client was connected to JEUS using SSL. This was caused due to the processing speed of the connected JEUS server being slower than the speed at which the client requests were sent.

  • Related Issue: IMS-184354, IMS-184207, IMS-184079

4.33. Fix for POST Request Error While Using RequestLevelPing

  • Fixed the error that occurred when sending the POST request body to JEUS while using RequestLevelPing in WJPv2.

  • Related Issue: IMS-178356

4.34. Fix for ERRORDOCUMENT Setting In VHOST Not Working

  • Fixed the issue where the ERRORDOCUMENT setting in the VHOST section wasn’t functioning properly, due to the ForceCacheModificationCheck setting being unable to locate the VHOST while generating the error message.

  • Related Issue: IMS-174041