Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 41640 invoked from network); 9 Jun 2010 19:26:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Jun 2010 19:26:33 -0000 Received: (qmail 92710 invoked by uid 500); 9 Jun 2010 19:26:29 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 92572 invoked by uid 500); 9 Jun 2010 19:26:29 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 92563 invoked by uid 99); 9 Jun 2010 19:26:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 19:26:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jun 2010 19:26:18 +0000 Received: from localhost (localhost [127.0.0.1]) by tor.combios.es (Postfix) with ESMTP id 5BF0C226246 for ; Wed, 9 Jun 2010 21:24:40 +0200 (CEST) Received: from tor.combios.es ([127.0.0.1]) by localhost (tor.combios.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4WEQI6aQSEk for ; Wed, 9 Jun 2010 21:24:40 +0200 (CEST) Received: from [192.168.245.129] (p549E2799.dip0.t-ipconnect.de [84.158.39.153]) by tor.combios.es (Postfix) with ESMTPA id F022F226242 for ; Wed, 9 Jun 2010 21:24:39 +0200 (CEST) Message-ID: <4C0FEAB5.4050807@ice-sa.com> Date: Wed, 09 Jun 2010 21:25:41 +0200 From: =?UTF-8?B?QW5kcsOpIFdhcm5pZXI=?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: HyperLink Office connection References: <1276015401.21404.ezmlm@tomcat.apache.org> <20100608202708.0a0543a6.antongiulio05@gmail.com> <4C0F644B.80507@ice-sa.com> <4C0FADBB.8080807@pidster.com> <4C0FB41E.5060701@ice-sa.com> <4C0FC7B4.3010800@pidster.com> <4C0FDCC3.4090703@christopherschultz.net> <99C8B2929B39C24493377AC7A121E21F98E51B729C@USEA-EXCH8.na.uis.unisys.com> In-Reply-To: <99C8B2929B39C24493377AC7A121E21F98E51B729C@USEA-EXCH8.na.uis.unisys.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Caldarale, Charles R wrote: >> From: Christopher Schultz [mailto:chris@christopherschultz.net] >> Subject: Re: HyperLink Office connection >> >> Or do you mean that Word has some kind of embedded web >> browser (almost certainly MSIE). > > Yes, MS Office products have done this for ages. IE is a just a rendering engine that can be invoked by pretty much any program to display HTML in any window the program provides. I think it's running as a separate child process rather than in-process, but I'm not positive about that. > Probably that is what is happening. Word has some embedded "browser capability" (using a part of IE's DLL's), but it probably does not support the full set of IE capabilities (like cookies e.g), which may be the reason of the OP's problem. Antonio : When Word is doing the login, Tomcat returns a re-direct response to the original requested page, along with a "Set-Cookie" header containing the session-id. However, Word does not take this Set-Cookie header into account, and does not send the Cookie header when it re-requests the protected page. So Tomcat thinks this is a new session, and sends the request somewhere else. Or something of the kind. You nmay have better luck using the setup whereby Tomcat does not use session-id cookies, but embeds the session-id in the URL. Someone here should intervene, and tell you how to achieve this. Anyway, this is all quite inelegant, and likely to cause variable behaviour depending on which browser version is installed, which local software is installed, which DLLs and so on. If this whole thing is supposed to work inside a local Windows-based network, for Windows workstations and users already logged-in into the Windows domain, then I would suggest that you redesign your scheme to work using the Windows Integrated Authentication (aka NTLM). I have not tried it, but I am quite sure that MS-Word will support this, and there are several solutions for supporting this in Tomcat. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org