I've seen this before on a fortigate firewall. The FW will detect "apt" as app:XMLRPC rather than app:HTTP for the purposes of "Application Detection" and if the "allow port 80 rules" is infact an "Allow only app:HTTP on port 80" rule , then XMLRPC over port 80 is disallowed.
David On Mon, Nov 4, 2019 at 4:13 PM Jamon Camisso via talk <[email protected]> wrote: > Well this is a new low: > > > https://askubuntu.com/questions/1185612/apt-get-stuck-on-waiting-for-headers/1185713 > > Mind-boggling that it is/was even an issue at an ISP & HTTP level. > > Either they have a giant whitelist of browser agents to maintain, or a > blacklist to update and added apt to it. > > In either case, they're looking at HTTP traffic and acting on it directly. > > Still an issue for anyone? > > Jamon > --- > Post to this mailing list [email protected] > Unsubscribe from this mailing list > https://gtalug.org/mailman/listinfo/talk > -- David Thornton https://wiki.quadratic.net https://github.com/drthornt/ https://twitter.com/northdot9/
--- Post to this mailing list [email protected] Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
