stream + content-length + chunking

If I understand Deb's explanation of the process correctly, it's not a limitation in the rule functionality, but a limitation of the scenarios.

 

 

The stream profile is fast because it doesn't buffer all of the content. As the full content isn't being collected before the substitution is done, you don't know what the content length will be after the substitution(s) are complete. Therefore, you can't set the content-length. To resolve this you need to use chunking.

 

 

If you want to avoid chunking and set the content-length correctly, then you have to buffer the full content. This can be done with TCP/HTTP::collect, but uses more resources to do.

 

 

Aaron