Opened on 03/08/18 at 04:11:03
Closed on 04/11/18 at 02:47:25
#3323 closed defect (fixed)
mhttpd's http etag can result in invalid caching in a browser.
Reported by: | Chris Johns | Owned by: | Chris Johns |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | lib | Version: | 5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | #3324 |
Description
The mhttp's http etag uses the mtime and file length and this can cause subtle issues if a target has no RTC or it is incorrect and files are being copied without preserving the mtime or changes happen that do not change the length.
The cp
and untar
code do not update a file's time.
Add support for an etag callback so a user can manage the tag, ie MD5 or something similar.
Change History (2)
comment:1 Changed on 03/08/18 at 04:12:12 by Chris Johns
Blocking: | 3324 added |
---|
comment:2 Changed on 04/11/18 at 02:47:25 by Chris Johns <chrisj@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
In d13a624/rtems: