Cisco Cisco Web Security Appliance S670
19
Release Notes for Cisco IronPort AsyncOS 7.5.0 for Web
Resolved Issues
72072
Fixed: Client applications get “sec_error_reused_issuer_and_serial” error when
accessing an HTTPS server that uses a certificate with the same serial number as
a different server’s certificate in some cases
accessing an HTTPS server that uses a certificate with the same serial number as
a different server’s certificate in some cases
Previously, client applications got a “sec_error_reused_issuer_and_serial” error when
accessing an HTTPS server under the following conditions:
accessing an HTTPS server under the following conditions:
•
The HTTPS server uses a certificate with the same serial number as a different
server’s certificate that the client application has already encountered.
server’s certificate that the client application has already encountered.
•
Decryption is enabled and the connection is decrypted.
This no longer occurs. Now, the HTTPS Proxy creates a unique serial number when
it mimics the server certificate when communicating to the client application in a
decrypted connection.
it mimics the server certificate when communicating to the client application in a
decrypted connection.
73535
Fixed: Web Proxy erroneously stops reading the entire uploaded object in a
POST request when it sends an HTTP 407 status code due to authentication
being required
POST request when it sends an HTTP 407 status code due to authentication
being required
Previously, the Web Proxy erroneously stopped reading the entire uploaded object in
a POST request when it sent an HTTP 407 status code due to authentication being
required. Many web browsers treat this behavior as an error.
a POST request when it sent an HTTP 407 status code due to authentication being
required. Many web browsers treat this behavior as an error.
This no longer occurs. Now, the Web Proxy finishes reading the uploaded content
before sending the 407 status code to the client.
before sending the 407 status code to the client.
75106
Fixed: Web Proxy erroneously stops reading the entire uploaded object in a
POST request when it sends an HTTP 307 status code due to authentication
being required in transparent mode
POST request when it sends an HTTP 307 status code due to authentication
being required in transparent mode
Previously, the Web Proxy was in transparent mode, it erroneously stopped reading
the entire uploaded object in a POST request when it sent an HTTP 307 status code
due to authentication being required. Web browsers treated this as an error and did not
redirect the page to allow authentication to occur.
the entire uploaded object in a POST request when it sent an HTTP 307 status code
due to authentication being required. Web browsers treated this as an error and did not
redirect the page to allow authentication to occur.
This no longer occurs. Now, the Web Proxy finishes reading the uploaded content
before sending the 407 status code to the client.
before sending the 407 status code to the client.
75296
Fixed: WCCP load balancing negotiation fails when the port numbers are not in
the same order in the same WCCP service ID on multiple Web Security
appliances
the same order in the same WCCP service ID on multiple Web Security
appliances
Previously, WCCP load balancing negotiation failed when the port numbers were not
in the same order in the same WCCP service ID on multiple Web Security appliances.
This no longer occurs.
in the same order in the same WCCP service ID on multiple Web Security appliances.
This no longer occurs.
Now, the web interface sorts the ports in the WCCP service ID before saving the port
numbers internally.
numbers internally.
75351
Fixed: Web Proxy erroneously sends only one cookie to the destination server
when a client request contains multiple cookies
when a client request contains multiple cookies
Previously, when a client request contained multiple cookies, the Web Proxy
erroneously sent only one cookie to the destination server. This no longer occurs.
erroneously sent only one cookie to the destination server. This no longer occurs.
Table 3
Resolved Issues in AsyncOS 7.5.0 for Web (continued)
Defect ID
Description