I simply lost a few days of labor to some crashes editor. My file has become a clear file, and also the last backup I've comes from 4 days ago.

I've the CSS file held in my Chromium's cache, however it appears like this:

http://myserver.example.com/style.css
HTTP/1.1 200 OK
Date: Mon, 04 Jul 2011 05:18:25 GMT
Last-Modified: Mon, 04 Jul 2011 01:10:47 GMT
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 7588
Content-Type: text/css
00000000: 5e 01 00 00 02 08 00 00 be 45 ba c7 cd 05 2e 00 ^........E......
00000010: 25 68 d9 c7 cd 05 2e 00 1d 01 00 00 48 54 54 50 %h..........HTTP
00000020: 2f 31 2e 31 20 32 30 30 20 4f 4b 00 44 61 74 65 /1.1 200 OK.Date
00000030: 3a 20 4d 6f 6e 2c 20 30 34 20 4a 75 6c 20 32 30 : Mon, 04 Jul 20
00000040: 31 31 20 30 35 3a 31 38 3a 32 35 20 47 4d 54 00 11 05:18:25 GMT.
(etc)
00000000: 1f 8b 08 00 00 00 00 00 00 03 cd 3d fd 8f db b6 ...........=....
00000010: 92 3f d7 7f 05 2f 8b 22 ed c2 f2 87 fc b1 6b 2f .?.../."......k/
00000020: 1a a0 09 5e 1e f0 5e 7b 57 34 c5 dd 0f 87 83 21 ...^..^{W4.....!
00000030: db f2 5a 89 6c f9 49 72 36 5b 63 ff f7 e3 b7 86 ..Z.l.Ir6[c.....
00000040: e4 50 1f 9b 4d ef 52 34 b1 65 71 66 38 1c ce 0c .P..M.R4.eqf8...
00000050: 87 c3 e1 f0 9a fc e3 9c 1e c9 3f e2 94 fc b1 8f ..........?.....

The whole file appears to become there, and that i could possibly get the written text.

Let me return the plain CSS file in some way. I attempted removing the information, but gzip states it is not gzip format. However it does not appear to become gzip encoded (it isn't binary, in the end...). Could it be base64 or something like that? I have were built with a difficult time coming up with any information on this.

Try locating the gzip header by removing the hex data into an editor and looking out for that header according to gzip specification. You need to have the ability to do that by locating the finish from the response body and choosing the prior 7588 bytes (you've this data within the response headers: Content-Length: 7588) - this ought to be the very first character from the header.

With respect to the flags occur the header, gzip'd files might be ASCII or binary. You are able to determine whether data are base64 encoded as base64 plan encodings terminate using the = character. You are able to decode base64 online.

Alternatively why not consider a tool for example ChromeCacheViewer.

The file looks gzip. It's the 1f8b header. Chrome stores the cached files as files, you need to simply locate them. Google for "location of chrome cache" and discover it for the platform.