Links display and extraction should use response header values
GoogleCodeExporter opened this issue · comments
At a minimum, the Location and Content-Location HTTP response headers need to
be processed and included in the results.
Original issue reported on code.google.com by gfleisch...@gmail.com
on 26 Jul 2011 at 6:52
Links display includes Location and Content-Location responses.
Additional refactoring would move this into HTML extraction/results generation
to populate universally.
Original comment by gfleisch...@gmail.com
on 14 Jul 2013 at 10:32
- Added labels: RAFT3
Fixed in RAFT3.
Original comment by gfleisch...@gmail.com
on 27 Jul 2013 at 9:30
- Changed state: Fixed