Welcome to ISAserver.org

Toruble with ZIP file in OWA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Exchange Publishing >> Toruble with ZIP file in OWA

Page: [1]

Message

<< Older Topic Newer Topic >>

Toruble with ZIP file in OWA - 2.Jun.2005 2:55:00 AM

jonathan_vella

Posts: 21
Joined: 15.Jan.2004
From: Malta
Status: offline

We have ISA2004 and Exchange 2003 on seperate machines. When we access OWA through our external domain name, we cannot open/save ZIP files. However, if we use the internal FQDN when inside our network, this works.
Any ideas please?

Post #: 1

Featured Links*

RE: Toruble with ZIP file in OWA - 2.Jun.2005 8:54:00 AM

tshinder

Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi Jonathan,

Check the ISA firewall logs to see what blocked the file.

HTH,
Tom

(in reply to jonathan_vella)

Post #: 2

RE: Toruble with ZIP file in OWA - 14.Jun.2005 3:38:00 AM

chrispriest

Posts: 1
Joined: 14.Jun.2005
From: London
Status: offline

Hello there,

We are getting exactly the same behaviour.

We think we have narrowed it down to the proxy as when you connect directly to the exchange server, you can open zips fine.

The HTTP policy for the rule has Extentions set to 'Allow all extensions'.

In the logs we get,

Action: Failed Connection Attempt
Error Information: 0x980
HTTP Status Code: 50
Cache Information: 0x100000

The user gets "Error Code: 500 Internal Server Error. The request is not supported. (50)" in their browser.

Help!

Chris

(in reply to jonathan_vella)

Post #: 3

RE: Toruble with ZIP file in OWA - 15.Jun.2005 5:25:00 AM

ClintD

Posts: 1833
Joined: 26.Jan.2001
From: Keller, TX
Status: offline

Each of you has published the OWA Server using the "Publish a Web Server" instead of the "Publish a Mail Server" wizard.

It's bogus, but the wizards are different.

The "Publish a Web Server" sets a property "SendAcceptEncodingHeader" to allow/disallow Compressed responses. When you run the Web Server wizard, it sets the property to block the encoding header responses - ZIP files are interpreted as compressed data and therefore get dropped.

Re-publish your OWA server using the Publish a Mail Server wizard and you will fix this.

There is no way to set this attribute without using a script - it's easier to just re-run the wizard.

To verify which wizard you really used, go into the rule and on the Traffic tab, select Filtering\HTTP Filtering. On the General tab, the options afor "Verify Normalization" and "Block High Bit characters" are set when you run the "Publish a Web Server" and cleared when you run the "Publish a Mail Server" - this is just an indirect way of determining which wizard you ran - neither of these options will fix this error.

[ June 15, 2005, 05:29 AM: Message edited by: ClintD ]

(in reply to jonathan_vella)

Post #: 4