@RichFelker @necrophcodr Not sure if this is worth rejecting client not supporting https though...
-
-
Replying to @ch3root
@ch3root@necrophcodr Just exempting UA==wget from the redirect would probably suffice to avoid practical problems.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@necrophcodr You mean busybox wget specifically? (It seems to have UA=="Wget" while ordinary wget has "Wget/VERSION".)2 replies 0 retweets 0 likes -
Replying to @ch3root
@ch3root@necrophcodr I was just assuming anyone who scripted a download knows which transport they want and expects it to be honored.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker This, or they just didn't have any choice because they scripted it before https was available.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@ch3root Sigh. I should take the https support in toybox wget and send BusyBox a copy, shouldn't I?1 reply 0 retweets 0 likes -
Replying to @landley1 reply 0 retweets 0 likes
-
Replying to @RichFelker
@landley@ch3root We really need to get development of@tlsify off the ground to make stuff like this (TLS in bb,toybox,etc.) doable right.2 replies 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@ch3root@tlsify I'm piping the data through a command line utility that converts HTTP into https. Don't really care which one.1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.