Interesting. Could you also post the request and response for the initial get request for the file? This format works perfect.
On Sep 2, 2017 14:51, "Lost Admin" <[email protected]> wrote: I think the 404 was a mis-type on my part and should have been 401 (unauthorized). As this was the first attempt to "save" I had not yet authenticated. Re-doing my testing, the 204 is as follows (this is the successful save of tiddlywiki): On Saturday, September 2, 2017 at 1:58:17 PM UTC-4, Arlen Beiler wrote: > Good afternoon, > What is the response headers for the request with the status code 204? And > why does the initial put request have a status of 404? > Thanks > > On Sep 2, 2017 1:29 PM, "Lost Admin" <[email protected]> wrote: > > Here you go ... This only covers the save, including the authentication > step (minus credentials) > > > *Initial PUT http://domain.dom/index.html > <http://domain.dom/index.html>Status code: 404* > > Response headers (296 B) > Date > Sat, 02 Sep 2017 17:19:45 GMT > Server > Apache/2.4.27 (FreeBSD) OpenSSL/1.0.1s-freebsd PHP/5.6.31 > Keep-Alive > timeout=5, max=99 > Connection > Keep-Alive > Content-Type > text/html > Request headers (452 B) > Host > domain.dom > User-Agent > Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/55.0 > Accept > */* > Accept-Language > en-US,en;q=0.5 > Accept-Encoding > gzip, deflate > Referer > http://domain.dom/index.html > Content-Type > text/html;charset=UTF-8, appli…orm-urlencoded; charset=UTF-8 > If-Match > "1eb890-5582095dd9986" > Content-Length > 2013328 > DNT > 1 > Connection > keep-alive > > > > *PUT http://domain.dom/index.html <http://domain.dom/index.html>Status > Code: 204Version HTTP/1.1* > > Request headers (499 B) > Host > ariel.suntrap.ca > User-Agent > Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/55.0 > Accept > */* > Accept-Language > en-US,en;q=0.5 > Accept-Encoding > gzip, deflate > Referer > http://domain.dom/index.html > Content-Type > text/html;charset=UTF-8, appli…orm-urlencoded; charset=UTF-8 > If-Match > "1eb890-5582095dd9986" > Content-Length > 2013328 > DNT > 1 > Connection > keep-alive > Authorization > Basic <redacted> > > *Now save again without reloading* > > > *PUT http://domain.dom/index.html <http://domain.dom/index.html>Status > Code: 412 Precondition Failed* > Response headers (262 B) > Date > Sat, 02 Sep 2017 17:27:15 GMT > Server > Apache/2.4.27 (FreeBSD) OpenSSL/1.0.1s-freebsd PHP/5.6.31 > Content-Length > 249 > Keep-Alive > timeout=5, max=100 > Connection > Keep-Alive > Content-Type > text/html; charset=iso-8859-1 > Request headers (499 B) > Host > domain.dom > User-Agent > Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/55.0 > Accept > */* > Accept-Language > en-US,en;q=0.5 > Accept-Encoding > gzip, deflate > Referer > http://domain.dom/index.html > Content-Type > text/html;charset=UTF-8, appli…orm-urlencoded; charset=UTF-8 > If-Match > "1eb890-5582095dd9986" > Content-Length > 2013314 > DNT > 1 > Authorization > Basic <redacted> > Connection > keep-alive > > On Friday, September 1, 2017 at 10:26:15 AM UTC-4, Arlen Beiler wrote: > >> Ok, well all I need is the request and response info for the put request. >> Actually, just the response headers. If you open your Developer Tools and >> go to the network tab, it will show you all the requests the page makes for >> everything. Find the put request it sends to save the file and click on it. >> It should show you the response headers. You can copy it here or email it >> to me directly if you like. >> >> On Fri, Sep 1, 2017 at 10:11 AM, Lost Admin <[email protected]> wrote: >> >>> Ah! you are ahead of me in figuring out what needs to be done. >>> Unfortunately, my javascript skills are nowhere near good enough to figure >>> out how to integrate the Apache way of doing things into TiddlyWiki. >>> >>> On Friday, September 1, 2017 at 9:47:32 AM UTC-4, Arlen Beiler wrote: >>>> >>>> I remember running into that when writing TiddlyServer. The apache >>>> webdav module should return some kind of revision string. The put saver >>>> expects an Etag, but this may not necessarily be what Apache sends. >>>> However, I believe that is where the problem is. >>>> >>>> On Fri, Sep 1, 2017 at 9:22 AM, Lost Admin <[email protected]> wrote: >>>> >>>>> Is there an easy way to get TiddlyWiki to re-read itself after saving? >>>>> >>>>> Apache tracks the time that you read the file and issues an error if >>>>> you try to save back to the server if the file on disk has a newer >>>>> timestamp. Which means: after I save changes to a file, it give me an >>>>> error >>>>> on subsequent changes unless I reload the wiki. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "TiddlyWiki" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/tiddlywiki. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/tiddlywiki/9084db99-3deb- >>>>> 446a-a6e3-d205ddc5269e%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/tiddlywiki/9084db99-3deb-446a-a6e3-d205ddc5269e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "TiddlyWiki" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/tiddlywiki. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/tiddlywiki/f2c207bb-f3de-44d6-9954-f5ad9bd0361c%40googlegroups.com >>> <https://groups.google.com/d/msgid/tiddlywiki/f2c207bb-f3de-44d6-9954-f5ad9bd0361c%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/tiddlywiki/ae7f53cc-1797-4a21-ae58-4c0c34437e79%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/ae7f53cc-1797-4a21-ae58-4c0c34437e79%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/ msgid/tiddlywiki/44825365-1645-45d8-beb1-47b7882428e5%40googlegroups.com <https://groups.google.com/d/msgid/tiddlywiki/44825365-1645-45d8-beb1-47b7882428e5%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTGWBuvXq%2B9un8gHeBO1WuupaW0GCWsvF8RGW42hsBJ_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
