Cisco Cisco Web Security Appliance S190

Página de 78
 
  Resolved Issues
30
Release Notes for Cisco IronPort AsyncOS 7.1.2 for Web
OL-23206-01
Resolved Issues in Version 7.1
 lists the issues that were resolved in version 7.1 of AsyncOS for Web.
73476
Fixed: W3C access logs stop logging data when it contains some fields in some 
cases
Previously, the W3C access logs stopped logging data when it contained the 
x-resultcode-httpstatus or x-hierarchy-origin fields in some cases. This no longer 
occurs. 
73615
Fixed: Web Proxy no longer includes the Content-Length header in server 
responses that cannot contain body content
Previously, the Web Proxy stopped including the Content-Length header in server 
responses that cannot contain body content, such as HTTP 204 responses. This breaks 
client applications that are not HTTP compliant. This no longer occurs. Now, the Web 
Proxy includes the Content-Length header when the destination server includes it in 
the response even if the response body cannot contain body data. 
73729
Fixed: Web Proxy erroneously responds with a 503 Service Unavailable response 
for responses with a Content-Length header value of 0 in some cases
Previously, the Web Proxy erroneously responded with a 503 Service Unavailable 
response when the response contained a Content-Length header value of 0 and the 
destination server ended the transmission using an atypical method. This no longer 
occurs. Now, the Web Proxy returns all data from the server to the client and returns 
the response code given by the server. 
73998
Fixed: Web Proxy does not follow servers that respond with a 302 Moved 
Temporarily HTTP response
Previously, the Web Proxy did not follow servers that responded with a 302 Moved 
Temporarily HTTP response. This no longer occurs. Now, the Web Proxy redirects 
client applications to the new URL specified in the 302 response. 
Table 4
Resolved Issues in AsyncOS 7.1.1 for Web (continued)
Defect ID
Description