Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

#3324 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: 4.11.4
Component: lib Version: 4.11
Severity: normal Keywords:
Cc: Blocked By: #3323
Blocking:

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 (1)

comment:1 Changed on 03/08/18 at 23:28:29 by Chris Johns <chrisj@…>

Resolution: fixed
Status: assignedclosed

In [changeset:"c3353ae565c3d3f9a605583b4c45abbdda7ac47b/rtems" c3353ae5/rtems]:

cpukit/mttpd: Add a callback to generate a per file HTTP etag.

Closes #3324

Note: See TracTickets for help on using tickets.