Bug#661425: ffproxy: can't handle invalid Last Modified HTTP header (breaks newegg.com)

Package: ffproxy Version: 1.6-9 Followup-For: Bug #661425 Dear Maintainer, I have prepared a patch which allows ffproxy to handle high characters (those in the range of 128-255) found in HTTP headers. This fixes the breakage on newegg.com. Cheers, Paul Merrill Description: Patch which allows

Bug#661425: ffproxy: can't handle invalid Last Modified HTTP header (breaks newegg.com)

Oops, sorry for all the attachments! Paul

Bug#661425: ffproxy: can't handle invalid Last Modified HTTP header (breaks newegg.com)

Package: ffproxy Version: 1.6-9 Severity: important Tags: upstream Dear Maintainer, ffproxy breaks images and javascript on newegg.com, making its many javascript-powered links unclickable. newegg.com sends an invalid Last Modified HTTP header of value file's last modified time, which ffproxy