Re: [RTEMS Project] #3323: mhttpd's http etag can result in invalid caching in a browser.

[RTEMS trac]

#3323: mhttpd's http etag can result in invalid caching in a browser.
-+--
 Reporter:  Chris Johns  |   Owner:  Chris Johns
 Type:  defect   |  Status:  closed
 Priority:  normal   |   Milestone:  5.1
Component:  lib  | Version:  5
 Severity:  normal   |  Resolution:  fixed
 Keywords:   |  Blocked By:
 Blocking:  3324 |
-+--
Changes (by Chris Johns ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"d13a62409e497c10725af6f975bdfb6ca17a3ebd/rtems"
 d13a624/rtems]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="d13a62409e497c10725af6f975bdfb6ca17a3ebd"
 cpukit/mttpd: Add a callback to generate a per file HTTP etag

 Close #3323.
 }}}

--
Ticket URL: 
RTEMS Project 
RTEMS Project
___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

[RTEMS Project] #3323: mhttpd's http etag can result in invalid caching in a browser.

[RTEMS trac]

#3323: mhttpd's http etag can result in invalid caching in a browser.
--+-
  Reporter:  Chris Johns  |  Owner:  Chris Johns
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  5.1
 Component:  lib  |Version:  5
  Severity:  normal   |   Keywords:
Blocked By:   |   Blocking:
--+-
 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.

--
Ticket URL: 
RTEMS Project 
RTEMS Project
___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs