I think I have found the problem.

A) and B) urls both give a 404 error when Tiddler import is attempted,
this seems to be due to the fact that TW is adding a "/" at the end of
the url, so the server is asked for a directory called TWindex.html
not a web page.

Here is the request header as sent by TW

GET /~j2fm/TWindex.html/?nocache=0.3450284512922786 HTTP/1.1
Accept: */*
Accept-Language: en-gb
x-requested-with: TiddlyWiki 2.4.1 (beta 3)

So how can I get TW to stop adding the "/" at the end?

 Cheers
         Jim J


On Jan 13, 11:51 pm, j2fm <jtwofm.ya...@j2fm.net> wrote:
> I have a TiddlyWiki located at
>
> A)http://mydomain.com/~j2fm/wiki/www/index.html
>
> This is also available (using Apache RewriteRule) at :-
>
> B)http://mydomain.com/~j2fm/TWindex.html
>        and
> C)http://mydomain.com/~j2fm/
>
> I have another TW (same TW version) stored locally and I would like to
> import a Tiddler from the on-line TW above.
>
> If I try importing from the above locations only url C) works, the
> other two give me an import error, no tiddlers are displayed.
>
> Checking the result produced by of the above 3 urls gives 3 identical
> files. ( I used wget and diff to check this).
>
> I then looked at the http headers, the only difference I could see was
> the Etag: value was slightly different for B) why I have no idea.
>
> A) ETag: "1600d5-520a4-bb1e1580"                       Fails
> B) ETag: "1600d5-520a4-bb1e1580;180db40"          Fails
> C) ETag: "1600d5-520a4-bb1e1580"                       Works
>
> I have tried both Firefox and MSIE7 and get the exact same result.
>
> Any ideas?
>
>     Cheers
>          Jim J
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to 
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to