Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"User-Agent:" shows up as part of the user agent in logs #147

Open
adiabatic opened this issue Sep 22, 2019 · 1 comment
Open

"User-Agent:" shows up as part of the user agent in logs #147

adiabatic opened this issue Sep 22, 2019 · 1 comment
Milestone

Comments

@adiabatic
Copy link

I see lines like this in my web server's log:

[redacted] - - [22/Sep/2019:19:15:01 +0000] "GET /twtxt.txt HTTP/2.0" 200 22082 "-" "User-Agent: twtxt/1.2.3 (+http://nblade.sdf.org/twtxt/twtxt.txt; @[redacted])"

twtxt is the only client that has User-Agent: in its User-Agent string.

Oddly enough, users who GET my twtxt file from IPv6 addresses don't have User-Agent: in their User-Agent strings. There are at least two users like this and both of them say they're using twtxt/1.2.3.

There are also users connecting from IPv4 addresses that have declined to say who they are on the twtxtiverse. Those User-Agent strings also (properly) lack the duplicated User-Agent: .

I had a look at the current generate_user_agent() and get_remote_tweets() but on a casual inspection I can't figure out what's causing this.

@buckket buckket added the bug label Nov 11, 2022
@buckket buckket added this to the 1.3.0 milestone Nov 11, 2022
@buckket
Copy link
Owner

buckket commented Nov 11, 2022

Strange, I just captured an outgoing HTTP request and the User-Agent header definitely does not contain the string "User-Agent".

Maybe your web server is adding this somehow?
Or we do have some other clients out there which identify themself as "User-Agent: twtxt/1.2.3 ".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants