Re: Cruisecontrol sometimes does not, send gzip Content-Type Header

Hi Michael,

Regarding use of gzip for old logs, the link below is what I was 
thinking about:

http://cruisecontrol.sourceforge.net/main/configxml.html#gzip	


You're using the jsp reporting app right? (Though I think you mentioned 
you also see this problem in the dashboard).
I've never seen this problem, but again, I don't know if gzip is 
explicitly used by CC elsewhere (though I'm not seeing it in a simple 
search of the source tree for "gzip").

Are you certain the stream data is actually "gzipped" when the header is 
omitted?

Is there any additional info you can provide? Maybe even steps to 
reproduce, with a config file, etc? (Even if it only happens "every 3rd 
time...").


Another wild guess:
 From the source code of the jsp reporting app 
(net.sourceforge.cruisecontrol.LogFile), I see this:

     /**
      * Whether the log file is compressed or not.
      * @return <code>true</code> if the file is compressed
      */
     public boolean isCompressed() {
         return getFile().getName().endsWith(LOG_COMPRESSED_SUFFIX);
     }
[where LOG_COMPRESSED_SUFFIX equates to ".xml.gz"]

So I'm wondering if the files being served that are "missing" the gzip 
header end with ".xml.gz"?

Dan




Date: Thu, 2 Jun 2011 10:48:06 +0200
From: Weibel Michael <[email protected]>
Subject: Re: [Cruisecontrol-user] Cruisecontrol sometimes does not
	send gzip	Content-Type Header
To: "[email protected]"
	<[email protected]>

Hi Dan,

Thanks for your answer.

 > >
 > > I'm not familiar with where/how CC uses gzip in the web interfaces, 
but
 > > I just wanted to make sure this is not a case of how CC will gzip
 > > logs/artifacts that are older than a certain age, but leave newer 
files
 > > uncompressed. Could that be what you are seeing?
I'm not sure what you mean.. I discovered it mainly on the newest build 
log, I did not check older builds.

 > >
 > > Other idea is the try running CC with -debug command and see if you 
can
 > > reproduce the problem, and maybe the console output will shed light on
 > > the cause.
It's reproduced every few page loads ;)
But I cannot see any different logging when a correct request is made or 
when an incorrect is made :( Even with the debug option on.

Any other ideas?

-Michael



------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2