Question

Wierd behaviour here folks and help to understand it would be appreciated. Basically I have set up reasonably standard TWiki test install. I do all my work on Firefox and then test with IE as that is our company standard.

Anyway when I want to edit a page in Firefox I get the editable page (no matter where the browser is). When I want to edit from IE on the server, it also works but

...if I try to Edit via IE from any other machine I get the IE error page 'Page cannot be displayed'. The same happens if I click on a ? next to an as-yet-uncreated Wikiword webpage. The same also happens if I try to attach anything but all the other buttons; 'Ref-by', 'Printable', 'Diffs', and 'More', all work as expected.

My apache error.log only gives the error

[notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!

Having read various support pages I have found that this is because my .htaccess file has the following line:

ErrorDocument 401 %nop%http://whr-p03170/bin/oops/TWiki/TWikiRegistration?template=oopsauth

Fine - I can understand that writing this URL differently would remove the error in the error log (how should the line be written?) but it begs the question why does trying to edit via IE from another system cause twiki to try and display the 401 page? (I'm also obviously not using %nop% correctly yet either )

Environment

-- SteveMayes - 07 Feb 2005

Answer

I don't know why IE doesn't work while others do, but the Error line should be something like

ErrorDocument 401 /bin/oops/TWiki/TWikiRegistration?template=oopsauth

As for nop that is a twiki specific operator, while .htaccess is for apache. None of the other TWikiShorthand will work there either. The correct use for nop, inside a twiki topic, is <nop>, for example %<nop>WIKIVERSION% yields %WIKIVERSION% .

-- MattWilkie - 07 Feb 2005

Thanks for the pointer on the use of nop Matt, and the line for .htaccess was also spot on. After a good nights sleep I returned to the IE problem and this will make you all chuckle (well it did me ) - to fix this fault with IE you have to modify it's default settings to......
...
...
make it HTTP1.1 compliant! (he he he). To do this select Tools\Internet Options from the Menu bar, then select the 'Advanced' tab and scroll down to the 'use HTTP1.1' option and select it. Apply, close and that's it, IE will now behave the way it should (at least in this respect).

-- SteveMayes - 08 Feb 2005

good, I'm glad it was that simple for you.

when I saw the title of this page I thought 'at last, I'm not alone! (WhatsWrongIE)' but alas, twas not to be.

-- MattWilkie - 08 Feb 2005

Just noticed that this still appears as a question asked but not yet answered. It was answered by myself above - the unanswered query is Matt's (WhatsWrongIE).

-- SteveMayes - 21 Mar 2005