Hi all, I changed the status from 302 to 308. I can now upload a small txt files but if I try to attach a file bigger than 1meg, I got the same issue as the begginning... The browser freeze and nothing happens. What else can I try ? Thanks. -----Message d'origine----- De : squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] De la part de Sebastien.Boulianne@xxxxxx Envoyé : 19 avril 2016 09:05 À : squid3@xxxxxxxxxxxxx; squid-users@xxxxxxxxxxxxxxxxxxxxx Cc : Marc-Andre Bouchard <marc-andre.bouchard@xxxxxx> Objet : Re: Attached file on OWA with Squid Hi Amos, Eliezer and all ;), As I wrote, if I connect to our VPN then I try to attach a file with the OWA, it works. If I forward all owa requests directly to the mail server, I can attach a file without any issues. I isolated the issue and we can see the problem happens when owa requests pass thru the Squid. Is it a server issue or a Squid issue ? Im running MS Exchange 2007 SP3 x64. Im using the very latest version of Squid. I will try to change the 302 status to 308. Thanks you very much for ur help guys. -----Message d'origine----- De : squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] De la part de Amos Jeffries Envoyé : 9 avril 2016 00:16 À : squid-users@xxxxxxxxxxxxxxxxxxxxx Objet : Re: Attached file on OWA with Squid On 7/04/2016 5:24 a.m., Sebastien.Boulianne wrote: > I configured my OWA to pass thru the Squid. > Auth work perfectly. > Browsing is working perfectly. > All is working perfectly except when I try to attach files or documents to an email. > > [cid:image002.png@01D19007.A7E26D20] > > > And It stops here. Nothing else happens. > > I did some tests and I noticed that happens when I am connecting from external to OWA. > If I connect to the VPN then I try to send an attached file with the OWA, it works. If you mean that you are using Squid through the VPN, then that probably means its not a Squid problem. > > Here is my config for my OWA. > > ### OWA > cache_peer owa.domain.qc.ca parent 443 0 no-query originserver > login=PASS ssl sslcert=/etc/pki/tls/certs/domain.qc.ca.cert.pem > sslkey=/etc/pki/tls/private/domain.qc.ca.key.pem > options=NO_SSLv2:NO_SSLv3:SINGLE_DH_USE:CIPHER_SERVER_PREFERENCE > dhparams=/etc/pki/tls/private/dhparams.pem > cipher=EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+E > CDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:E > DH+aRSA:HIGH:!RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS > name=owa acl owahttps url_regex ^https://owa\.domain\.qc\.ca > cache_peer_access owa allow owahttps http_access allow www443 owahttps > acl owahttp url_regex ^http://owa\.domain\.qc\.ca http_access deny > owahttp deny_info 302:https://%H%R owahttp You probably need to use 308 status here. 302 tells the client to try again using the *GET* method. Sending of things is not a GET action. > > Thanks you very much for your advice. > What version of Squid (squid -v) ? Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
