Closed Bug 1219056 Opened 9 years ago Closed 8 years ago

/api/2/user/<username> doesn't work if the user name contains a dot(.)

Categories

(support.mozilla.org :: Users and Groups, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dvlcornelis, Assigned: rehandalal+mozilla)

References

Details

(Whiteboard: u=user p=1)

/api/2/user/<username> doesn't work if the user name contains a dot(.)
Other cases (e.g. involved=<username>) I tried work, so possibly only user is affected.
Noticed it with this user: /questions/1085818
Created a test account (cor-el.test) and that fails as well.
Works OK with the normal forum link for a user profile (/user/<username>).
When you say "doesn't work", what do you see? I'm getting a 404 when I test it here. Is that right?
Yes, that is right.
If you open the page via the location bar then you get a 404 error.
Via XHR I see a "NOT FOUND" response.
[HTTP/1.1 404 NOT FOUND 585ms]

I don't know what other delimiter characters are allowed in a user name apart from a hyphen (-) and an underscore (_).
Confirming as The API is also not working for me
https://support.mozilla.org/api/2/user/Safwan.rahman returning a 404 Error
Status: UNCONFIRMED → NEW
Ever confirmed: true
As I suspected, its a issue with the Django 3.x Upgrade, but actually its not.
I have tested with pre update and it seems that the issue is also present there
Blocks: 1183424
Mike, Brittany, is this something we need to fix before moving to the new AAQ flow?
Whiteboard: u=user p=?
(In reply to Kadir Topal [:atopal] from comment #6)
> Mike, Brittany, is this something we need to fix before moving to the new
> AAQ flow?

As its not possible to get information of user having username with dot by using the API, The AAQ flow can not verify if the user is logged in. So the user who has username with dot may can not post any question. So this need to be fixed before moving to the AAQ flow
Pretty easy to fix this. 1pt assigned.
Whiteboard: u=user p=? → u=user p=1
Assignee: nobody → rdalal
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.