Argl. According to https://en.wikipedia.org/wiki/HTTP_404, 404 means "Not found". Thus we could read the yellow lines as
code: 404, message "File not found" This fits the missing favicon.ico situation. Am Sonntag, 29. Dezember 2019 12:16:38 UTC+1 schrieb UBi: > > Hi Mohammad, > > as you can see on the line following the yellow lines, your browser > automatically tries to fetch a favicon.ico file. > If there is none, the server sends a 404 error code, usually accompanied > by a short description. > It seems that in this case resolving the code to a description went wrong. > I can't tell you why, I'm not that familiar with the > SimpleHTTPRequestHandler innards. > > Am Sonntag, 29. Dezember 2019 08:10:02 UTC+1 schrieb Mohammad: >> >> The script works fine, I am just curious about the message 404 appears on >> terminal window. I have highlighted them. >> >> Mohammad@6600K C:\TW\201. Python server >> >> $ python server.py >> >> 127.0.0.1 - - [29/Dec/2019 09:14:54] "GET / HTTP/1.1" 200 - >> >> 127.0.0.1 - - [29/Dec/2019 09:14:54] code 404, message File not found >> >> 127.0.0.1 - - [29/Dec/2019 09:14:54] "GET /favicon.ico HTTP/1.1" 404 - >> >> 127.0.0.1 - - [29/Dec/2019 09:15:37] "GET /wikis/ HTTP/1.1" 200 - >> >> 127.0.0.1 - - [29/Dec/2019 09:15:40] "GET /wikis/tw.html HTTP/1.1" 200 - >> >> 127.0.0.1 - - [29/Dec/2019 09:15:41] "OPTIONS /wikis/tw.html HTTP/1.1" >> 200 - >> 127.0.0.1 - - [29/Dec/2019 09:15:42] code 404, message File not found >> >> 127.0.0.1 - - [29/Dec/2019 09:15:42] "GET /wikis/favicon.ico HTTP/1.1" >> 404 - >> 127.0.0.1 - - [29/Dec/2019 09:16:16] "PUT /wikis/tw.html HTTP/1.1" 200 - >> >> 127.0.0.1 - - [29/Dec/2019 09:16:16] "HEAD /wikis/tw.html HTTP/1.1" 200 >> - >> 127.0.0.1 - - [29/Dec/2019 09:41:05] "GET / HTTP/1.1" 200 - >> >> 127.0.0.1 - - [29/Dec/2019 09:41:06] code 404, message File not found >> >> 127.0.0.1 - - [29/Dec/2019 09:41:06] "GET /favicon.ico HTTP/1.1" 404 - >> >> >> >> >> On Sunday, December 29, 2019 at 1:30:42 AM UTC+3:30, UBi wrote: >>> >>> I will describe my use case on Linux, Windows should work in a similar >>> fashion. >>> >>> My TiddlyWiki files live in /home/ubi/TW, abbreviated ~/TW. There I >>> placed the script as twserver.py. >>> For a first test, I started it manually in a terminal window: >>> >>> /usr/bin/python3 ~/TW/twserver.py >>>> >>> >>> Then I pointed my browser to http://localhost:8080/. Status messages >>> started appearing in the terminal window. >>> >>> In the browser window a list of files and directories below ~/TW >>> appeared. >>> >>> I opened one of my TW files, notes.html, and created a new Tiddler. The >>> I saved the changes. >>> This >>> 1) backed up ~/TW/notes.html html to >>> ~/TW/twBackups/notes.html.YYYYMMDDhhmmss, creating ~/TW/twBackups on the >>> fly. >>> 2) saved the changes to ~/TW/notes.html. >>> >>> Now I have to find out how / where I can add a call to the script to my >>> startup or login procedures. >>> >>> HTH UBi >>> >>> >>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cb7b65a8-2d5a-4187-bc98-31de83a44563%40googlegroups.com.
