Hi Guys,
I expericene a rewriting problem with an SA 2000 and a sharepoint website. I operate an internal sharepoint server (WSS 3.0) and use our SA 2000 (with IVE OS 6.3 R1) to publish it. I created a web resource profile of type Microsoft sharepoint. I filled out the necessary fields (Base URL, SSO, etc.) and created the book mark.
When I try to access the bookmark, the sharepoint site is displayed fine. But, if I try to open a word document stored in a sharepoint document library word opens and displays the IVE sign in page instead of the document.
I used HTTP analyzer V3 to track what URL Word tries to open. To cut a long story short: Word uses an URL that misses the DanaInfo part.
LetÕs say the internal address of the sharepoint web site would be http://sharepoint, that I created a document library lib1, and I stored a word document called test1.doc in it. Then the internal URL of the word document would be:
http://sharepoint/lib1/test1.doc
Say that the IVE is reachable through https://ive1. The correct link to reach the word document would be https://ive1/lib1/,DanaInfo=sharepoint+test1.doc
Instead Word tries to open https://ive1/lib1/test.doc. The IVE responses with an HTTP 302 and a redirect URL to https://ive1/dana-na/auth/welcome.cgi what is exactly the login page that Word opens and displays instead of my doc.
Has anyone of you expericend the same problem?
Kind regards,
Dominik
Solved! Go to Solution.
I solved the issue myself. KB11282 (http://kb.pulsesecure.net/KB11282) pointed me in the right direction. Although both DLLs were registered correctly, putting the public URL into the Trusted Site zone in Internet Explorer (as offered in KB 931509 http://support.microsoft.com/kb/931509/en-us/) solved the issue.
Anyway an interessting issue. Maybe someone of you can provide a more detailed background about what is happening.
Regards,
Dominik
I solved the issue myself. KB11282 (http://kb.pulsesecure.net/KB11282) pointed me in the right direction. Although both DLLs were registered correctly, putting the public URL into the Trusted Site zone in Internet Explorer (as offered in KB 931509 http://support.microsoft.com/kb/931509/en-us/) solved the issue.
Anyway an interessting issue. Maybe someone of you can provide a more detailed background about what is happening.
Regards,
Dominik