Netscaler Knowledgebase

Rewrite has been "supported" since it was released, however, that doesn't mean that it worked as well as it should.  As issues were reported and corner cases isolated, they have been fixed.  The newer the builds, the more reliable it should be.  More to the point is if it was recommended to use it, and it has matured to the point where it is usable in many situations.  Be careful of interactions with other features though, in particular less used features if you use body rewrite, but I think that it has gotten to be fairly reliable based on my experience (the http 1.0 downgrade thing helps enormously).

The Oracle

# downgrades HTTP request to 1.0 to prevent chunking
# does NOT prevent HTTP keepalive from operating, due to keepalive headers
# can help avoid bugs that have cropped up as well when a server sends a malformed chunk
add rewrite action downgrade_1.0 replace http.req.version "\"HTTP/1.0\""
add rewrite policy to_1.0 true downgrade_1.0
bind rewrite global to_1.0 10 NEXT -type REQ_DEFAULT

The Oracle

I've got trouble with CMP in dynamically generated documents,

i try this

Add rewrite action http_down_1.0 replace HTTP.REQ.VERSION.MINOR "\"0\""

and it avoids HTTP 1.1 chunkin

Rewrite saves my life¡¡

Can you clarify the issue?  I am guessing that this relates to server chunked content where the server isn't generating a zero length chunk at the end, but is instead closing the connection.  With CMP turned on, this is resulting in an error, while without it, the page loads fine?  In such a case, disabling chunking with a 1.1->1.0 downgrade is perfectly reasonable, as:
1.  The connection is going to close anyway
2.  The server isn't sending enough data to verify at the HTTP level that the chunking is complete

The downgrade can also be done selectively for particular URL's if you wish.

The Oracle

...and of course, without CMP the page (pdf/rtf generated documents) loads fine