I had the same behavior:

Problem:  Files with no file extension (for what?, it has an HTTP mimetype!),
so the browser knows how to handle ..

But without HTTP (offline), there are some problems:

* mimetype is text/plain but it will be saved with the extension .html
* v3.40-2 and v3.43 both save it with the wrong extension (html)

* v3.33 (currently downloadable as previous version) add ".txt" extension -
  which is more comfortable

--> so to me it looks like a bug. <--

Seems the mimetype configuration page doesn't show the correct way ...

This "<---->" implicitly says to me, that the file extension will be
replaced/added dependent on the MIME type  -> visa versa.
BUT: It only executes it in one direction: Check the extension and then set
the
mimetype for it (manually) -> based on that mimetype set HTTrack's default
file
extension for that file.

Is it possible that HTTrack had forgotten how to look in the delivered mime
type from the source?

Proposal
--------
* would be fine if I could configure the behavior of adding file extensions
  depending of HTTP mimetype *AND* the original file extension.

i.e.
1) mime: text/html , original file extension: .html --> no change
2) mime: text/plain, original file extension: .html --> no change

3) mime: text/html, no extension --> optionally use original (no) extension
								 or force configured extension (.html)
4) mime: text/plain, no extension --> optionally use original (no) extension
								 or force configured extension (.txt)

5) misconfigured HTTP-Server:
mime: text/plain, original file extension: .html
	  			  		   --> parsing or not?	  			  		   --> what kind of extension?