Printer FriendlyEmail Article Link

Why content length is not included in HTTP responses from Landslide, when using HTTP DMFs from Basic Library?


Wireshark is expecting a “Content-Length” in the HTTP header. While Wirshark treats it as a mandatory field, in the Landslide Basic Library DMF implementation it is not. The basic library in Landslide is intended to be a basic “template”. If the library had a Content-Length in the template, the Content-Length would have to be updated each time someone “padded” the response. With no padding the Content-Length would be 0.  With padding it becomes a variable (dependent on the padding).  In Landslide Basic Library, we simply omit it and thus prevent any conflict with the body length and the content length value. To simply change the “basic” library to suite one customer’s request violates our “basic” library principle.

Product : 7100,Landslide,DMF,Landslide,HTTP,Packet Captures