71–80 of 80 posts
This makes it difficult to share links to info on some products in forums, chat or a Wiki -- because the recipient may not be from the same country as I am.
See also: https://xkcd.com/869/ for a variation of the same problem.
Earlier quoted context omitted.
Jeez that's a heck of a redirect chain. The :443 is an odd choice no? And the redirect to https://domain before https://www.domain . There are even two more for me. Also... inconsistent casing for the Location header? Different parts of the server stack I suppose. Location: https://logitech.com:443/mx location: https://www.logitech.com:443/mx location: https://www.logitech.com/en-us/mx.html location: https://www.logi…
443 is just the default https port, so not really? It doesn't add anything as browsers use that port by default when the scheme is https.
So if I split up a resource into two new resources, where should the old link point to? It seems to me never changing URLs could only ever fully work for applications where the datamodel never changes.
https://domain/customresource/ ---> https://domain/newresource-a/ https://domain/newresource-b So if I split up a resource into two new resources, where should the old link point to? It seems to me never changing URLs could only ever fully work for applications where the datamodel never changes.
https://domain/customresource/ ---> https://domain/newresource-a/ https://domain/newresource-b So if I split up a resource into two new resources, where should the old link point to? It seems to me never changing URLs could only ever fully work for applications where the datamodel never changes.
Not that long ago I clicked on a link that Microsoft provided somewhere in Windows -- could have been the event log, I don't remember. I do remember it was for a specific support article, but it ended up at a generic landing page for something. I am not talking about a link from Windows 95, it must have been Windows 10. But regardless, it is all gone. Then again, it probably wasn't a cool URL to begin with. It's amaz…
Very uncool; Microsoft even uses an URL shortener for most of their links (from windows etc) so that they can theoretically change where the user ends up at if the original page is replaced for whatever reason. But they shouldn't. Microsoft especially should make all of their documentation pages plain static HTML pages and keep them available forever. But also, any Windows documentation can live offline in the OS its…
The Event Log fwlinks still append the `ProdName=MicrosoftWindowsOperatingSystem` to the URL and the Microsoft Support homepage just ignores them helpfully asking "What do you need help with today?" and putting Windows on the second row of a 5 column grid.
Open the Event Viewer, click on an event and click the blue "Event Log Online Help" hyperlink at the bottom. I'll be willing to bet it won't matter what event you pick, you'll still end up at the Microsoft Support homepage.
Others take you on a roundabout journey to the Microsoft homepage.
> GET /fwlink/?LinkId=52884 HTTP/1.1
GET /products/ee/transform.aspx?[snip] HTTP/2
> GET /fwlink/?LinkId=528884 HTTP/1.1
Earlier quoted context omitted.
MX4 finally got me looking elsewhere until I stumbled upon this: https://ergodriven.com/products/the-vertical-handshake-mouse I got it specifically because they had a mini rant about the weight of switches that other vertical mice use, and while I couldn't tell if that was a real problem, that's the kind of mentality I used to ascribe to Logitech. The MX4 is clearly marketing logic. The haptic feature adds nothing of…
The hand is very off putting, should have hired a better hand model. Also real infomercial vibes, the way the posture completely changes between flat and vertical.
Earlier quoted context omitted.
Might have been an overeager packaging designer that printed that and then filed a ticket for someone to set up the redirect and that ticket is still in the person's queue. Or it's something about your own connection. Maybe an ad blocker? For me, the redirect works: $ curl -IL logitech.com/mx 2>/dev/null | grep http Location: https://logitech.com:443/mx location: https://www.logitech.com:443/mx location: https://www.…
Jeez that's a heck of a redirect chain. The :443 is an odd choice no? And the redirect to https://domain before https://www.domain . There are even two more for me. Also... inconsistent casing for the Location header? Different parts of the server stack I suppose. Location: https://logitech.com:443/mx location: https://www.logitech.com:443/mx location: https://www.logitech.com/en-us/mx.html location: https://www.logi…
But the rest could have been flattened into the second redirect.