This, I tried for 3 hours with hfs 299-1/2 (the pre-release).
After upgrading to the official hfs 300, the remove headers command worked for cookies, not for etag.
That's why I've already reported this issue
here.
can you give some examples to reproduce in order to find a solution
You have several ways of view
HTTP Headers:
1) The easiest way to reproduce this, is using
Chrome. Open a new blank tab. Right click anywhere and select '
Inspect element' and then click on '
Network'. Close HFS and save the '
HFS.Events' file contained on the
attached ZIP file in this post (or write in 'HFS.Events' any of these two filters described
here). Open HFS, add some files (images or any other file), and go back to Chrome, paste the URL and watch the Network activity. To view the HTTP Header of any request, do right click on '
Copy response headers' on any element you want (and paste it on Notepad to view it). You will notice that any element generated by HFS on-the-fly will be fine, without the '
ETag', but if you request (click) on some file (to view it, or download it), then the '
ETag' is NOT removed (only
Set-cookie is removed).
2) Another way is using
FlаѕhGеt (being the version 1.65, the last
adware-free version, which I'm currently using and you can download from
here), or else using some
HTTP Header view (online service), like
this or
this tool. If you use
FlаѕhGеt, you need to configure it at the lowest possible speed (to being able to see the HTTP headers in the log), going to:
Tools >
Options >
Connection >
Traffic usage in manual mode (b/s): 400. And then go again to:
Tools >
Speed Limit Mode >
Manual. And finally try to download (and quickly pausing it, to keep the logs at sight), a file that match some of those rules (as described on the point number one).
For example, a normal file listing request (it's working OK):
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 1890
Accept-Ranges: bytes
Server: HFS 2.3m
Cache-Control: no-cache, no-store, must-revalidate, max-age=-1
Content-Encoding: gzip
Content-Length: 1890
But viewing a static HTML file (the same as if you download other file):
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 123
Accept-Ranges: bytes
Server: HFS 2.3m
ETag: 6ED8C82CA55F6D57FECD5F712EFFF8F1
Last-Modified: Fri, 20 Apr 2018 20:30:40 GMT
Content-Disposition: filename="SomeWebPage.html";
Viewing/downloading a image file:
HTTP/1.1 200 OK
Content-Type: image/jpeg
Content-Length: 123456
Accept-Ranges: bytes
Server: HFS 2.3m
ETag: F48480F7C42C4CF548855994DF1B5191
Last-Modified: Fri, 20 Apr 2018 20:10:00 GMT
Content-Disposition: filename="SomeImageFile.jpg";
Summarizing: if you remove a header on
[+download] it works, but on
[+request] it doesn't do it properly (only removes '
Set-cookie' but
not the '
ETag'). I personally don't need this feature, but since
danny and
User21 wanted it, perhaps it's a easy fix.
Well, that's it, I hope this is useful...
> Off-topic: This gives an idea that it would be great to have a HFS template that shows the response HTTP Headers of a given URL (perhaps using part of the remote upload code?), among other useful information, like the client's User Agent, screen resolution, etc (something like THIS). I leave the idea here if someone wants to do it.