Wordle.net "Not in GZIP Format"

[Iain.Faulkner]

Afternoon all,

 

Bit of an urgent one this.

 

Teacher wants to use an image created using wordle for tomorrow's lesson (we have ofsted in, so ask no more :-) )but we keep getting hit by an error.

 

Image creates ok, but once you save it to the public gallery you can't view it anymore. The error we get is "Not in GZIP Format".

 

I've never come across this before, has anyone seen this? I've updated java on the machine in question, but still get the same.

 

It does, however, work when logged on as me. So it may be an access right issue.

 

I'm particularly interested in anyone who's had this problem that uses smoothwall. Apparently this used to work a few months ago the last time she used it, but since then we have installed smoothwall and I'm wondering if there is something I need to setup there to allow this through.

 

Any suggestions, as always, are greatly appreciated.

[6Foot2]

I feel the need to bump an old thread so here goes.

 

I have just had an E-Mail from a member of staff about Wordle.

 

Upon investigation I find that the error is the same as the one reported above [Not in GZip format] It is not a Java issue as our browsers pass Wordle's own Java test. All of our users on all our stations get the error [including administrator]

 

We get the error when trying to load a Word Cloud directly from Wordle - Beautiful Word Clouds However it will allow us to create a new Word cloud bu not save it [http://wordle.appspot.com/show is blocked by our LEA: Perhapos the answer lies there?]

 

Browser: Internet Explorer: 32 bit

O/S: Windows 7: 64 bit

 

@Iain.Faulkner: Were you able to resolve this?

[Iain.Faulkner]

No I didn't get any further with it unfortunately

[6Foot2]

OK. Thanks. Worth a try.

[jonnykewell1]

we have all sorts of problems with Java and wordle, some of our users can't even get to the create page, or when they press create type the text and press go nothing happens. I notice errors on page when in Internet explorer 8 on XP. any ideas?

[grant_girdwood]

If it is something to do with the filtering by your LEA try running the upload using browser development tools and taking a network capture (F12 in IE, CTRL + SHIFT + I in Chrome) and look at the network components which will show each request and the HTTP response code (there could be something in the back-end that is being blocked)

 

Also try running a Wireshark network capture and interrogate this to see if there is a sub-component being blocked which may cause this error.

 

Cheers!

[jonnykewell1]

Thanks Grant, I certainly agree it is our LEA, trying to get them too accept this is another matter, will run a wire shark and see if I can make sense of it lol.