WordPress.org

Making WordPress.org

Opened 3 months ago

Closed 7 days ago

Last modified 7 days ago

#4631 closed defect (fixed)

Invalid profile URLs should return a 404

Reported by: jonoaldersonwp Owned by:
Milestone: Priority: high
Component: Profiles Keywords: seo
Cc:

Description (last modified by jonoaldersonwp)

It appears that the current process of deleting (presumably spammy) profiles, such as https://profiles.wordpress.org/pornstarshop/ results in a 302 redirect to https://wordpress.org. This should be altered to use a 301 redirect for both future and existing redirects.

Change History (9)

#1 @jonoaldersonwp
3 months ago

  • Description modified (diff)

#2 @Otto42
3 months ago

User profiles are not deleted or removed. The example you give doesn't exist and never has, as far as I can tell.

A recent blocked account would be https://profiles.wordpress.org/admindevelopers/ for example. As you can see, no redirect or other indications that it is blocked.

#3 @SergeyBiryukov
3 months ago

  • Component changed from General to Profiles

#4 follow-up: @jonoaldersonwp
3 months ago

Ah, looks like this happens on any invalid request. E.g.,
https://profiles.wordpress.org/asdasdasdasdasdasddfghgreaergsgreagraregre.

Could we make these serve a clean 404 page, with a 404 HTTP status, and no redirect(s) please?

#5 in reply to: ↑ 4 @dd32
13 days ago

  • Summary changed from When profiles are deleted/removed, they should 301, not 302 to Invalid profile URLs should return a 404

Replying to jonoaldersonwp:

Could we make these serve a clean 404 page, with a 404 HTTP status, and no redirect(s) please?

Due to the mess that is Profiles, that's not currently possible without opening a _very_ large can of worms (trust me on that).

#6 follow-up: @jonoaldersonwp
13 days ago

Damn. I'm inclined to suggest that we still aim to resolve this; the current behaviour is pretty harmful.

#7 in reply to: ↑ 6 @dd32
13 days ago

Replying to jonoaldersonwp:

Damn. I'm inclined to suggest that we still aim to resolve this; the current behaviour is pretty harmful.

While I agree, I'm not re-architecting Profiles at this time.
It's a pretty blunt redirect at a very low level to prevent a lot of WordPress & BuddyPress functionality from operating - even replacing it with an equally blunt 404 didn't work out too well.

#8 @dd32
7 days ago

  • Resolution set to fixed
  • Status changed from new to closed

Found a bigger sledge hammer. Fixed in rr15407-dotorg.

A 404 template now exists, and the root-level page redirects to either your own profile or wordpress.org.

#9 @jonoaldersonwp
7 days ago

Wooo! Nice one :)

Note: See TracTickets for help on using tickets.