Skip to content

Broken links #1815

Closed
Closed

Description

@svick

While trying to fix broken links (#1814), I encountered several that I couldn't fix. Either their targets should be fixed, or the links should be removed.

Activity

  1. guardrex commented on Mar 28, 2017

    @guardrex
    Contributor

    Side Note: I never got around to it over in the ASP.NET Core docs, but there were quite a few 301 redirects over there (e.g., http://twitter.com should be https://twitter.com). I haven't done the analysis over here for redirects. It's a separate issue perhaps, but I was just wondering if when you did your broken link analysis if you witnessed a lot of 301's as well?

  2. svick commented on Mar 28, 2017

    @svick
    MemberAuthor

    @guardrex Looking at it now, there seems to be a lot of 301s, starting with 23 of them just on the main page. And the vast majority of those are due to a missing trailing slash (e.g. https://docs.microsoft.com/en-us/dotnet/articles/core is 301 pointing to https://docs.microsoft.com/en-us/dotnet/articles/core/). Personally I don't think those are worth fixing.

    Though I guess other redirects, like https://azure.microsoft.com/documentation/services/storage/, which is 301 pointing to https://docs.microsoft.com/en-us/azure/storage/ (with a 302 detour to https://azure.microsoft.com/en-us/documentation/services/storage/) might be worth it.

    I haven't looked at redirects any further though.

    In case you're interested, the code I used for broken links is here.

  3. guardrex commented on Mar 28, 2017

    @guardrex
    Contributor

    Personally I don't think those are worth fixing.

    Roundtrips suck! lol 😀 I'd fix all of them. I'm a bit of speed freak, so I don't like anything that slows anything down.

    DotnetCoreDocsWalker

    Ah ... that's very interesting. I use Xanu ... must be their 👽 influences 😄, but I look forward to taking a closer look at your DotnetCoreDocsWalker.

    @mairaw If you'd like an issue to fix 301's, let me know and I'll open one for it.

  4. mairaw commented on Mar 28, 2017

    @mairaw
    Contributor

    @guardrex can't we use this issue for that? I personally prefer going straight to the topic avoiding 301 redirects, if possible.

    @mikeblome are you guys deleting content without establishing 301 redirects for them in the VS docs?

  5. guardrex commented on Mar 28, 2017

    @guardrex
    Contributor

    Sure. I just didn't know if it was something you wanted to table for a later date.

    Yes, indeed on 301's ... eee ... yuck! 😀 ... and they have quite a few over in ASP.NET Core docs IIRC. I'll check both sets of docs and talk to Tom about the ones over there and report back here what I find out.

  6. mairaw commented on Mar 28, 2017

    @mairaw
    Contributor

    Yes, it could go to the backlog. I recently had to add all the pages where we missed the 301 redirects in our repo. They do run reports and open bugs for those internally and also on 404's (although I haven't seen a recent version of a 404 report).

  7. mikeblome commented on Mar 28, 2017

    @mikeblome
    Contributor
  8. added this to the Backlog milestone on Mar 28, 2017
  9. mairaw commented on Mar 28, 2017

    @mairaw
    Contributor

    @mikeblome this is the commit that @svick pointed to in the VS repo: MicrosoftDocs/visualstudio-docs@c2afa3e

    This broken a bunch of our links to the VS docs.

  10. mikeblome commented on Mar 28, 2017

    @mikeblome
    Contributor
  11. guardrex commented on Mar 29, 2017

    @guardrex
    Contributor
  12. mairaw commented on Sep 3, 2019

    @mairaw
    Contributor

    I've opened PR #14192 to fix the redirections on the homepage.

    I think most of the other redirections and broken links were already fixed throughout the years.
    The only exception I found is the last bullet:

    But I'd prefer if we open a separate issue for that alone so that we can decide what to do with that article. It requires an update rather than a simple link fix.

    Sounds good @svick?

  13. added
    needs-more-infoNeeds more info from OP. Auto-closed after 2 weeks if no response. [org][resolution]
    on Sep 3, 2019
  14. svick commented on Sep 7, 2019

    @svick
    MemberAuthor

    @mairaw Sounds good to me.

  15. removed
    needs-more-infoNeeds more info from OP. Auto-closed after 2 weeks if no response. [org][resolution]
    on Sep 16, 2019
  16. modified the milestones: Backlog, September 2019 on Sep 16, 2019
  17. self-assigned this
    on Sep 16, 2019
  18. mairaw commented on Sep 16, 2019

    @mairaw
    Contributor

    Ok, thanks @svick! Closing this one then and opened #14467 to take care of the remaining issue.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions