I wasn't aware of a few
User-Agent Formats.And I'm checking that
timeline is not sending those headers. I should push a change on that soon.
I wasn't aware of a few
And I'm checking that
I wasn't aware of a few
User-Agent Formats.And I'm checking that
timeline is not sending those headers. I should push a change on that soon.
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
https://eapl.mx/twtxt.txt in your log file?If you want more eyes on the agent, you can tell tell me, as I was thinking on something similar to catch those 'following requests'.
https://eapl.mx/twtxt.txt in your log file?If you want more eyes on the agent, you can tell tell me, as I was thinking on something similar to catch those 'following requests'.
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
Also reading the code, I see it creates two files, but I'm not sure which you are using now:
http://darch.dk/twtAgent.log <- 403 Forbidden
and
http://darch.dk/twtAgent.csv <- Not found here
Also reading the code, I see it creates two files, but I'm not sure which you are using now:
http://darch.dk/twtAgent.log <- 403 Forbidden
and
http://darch.dk/twtAgent.csv <- Not found here
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
Discovrability dilemma, but either I'm doing something wrong or (maybe) we have some PHP module(s) missing. I gave it a try and it returns the twtxt file content as expected when visited directly, yet there's no logs/log files created. + I'm still not sure why my htaccess redirection doesn't work x') ... Will keep you posted.