Closed Bug 622879 Opened 14 years ago Closed 13 years ago

Changing account email gives html 401 unauthorized html

Categories

(Cloud Services :: Server: Registration, defect)

Product:
Cloud Services
Component:
Server: Registration
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: telliott, Assigned: tarek)

Details

curl -d 'changed@mozilla.com' https://fczol3ywuinssxky6f2mqb4ihgs3he7nzspdl4h:curltest@stage-auth.services.mozilla.com/user/1.0/wuinssxky6f2mqb4ihgs3he7nzspdl4h/email

produces:

<html>
 <head>
  <title>401 Unauthorized</title>
 </head>
 <body>
  <h1>401 Unauthorized</h1>
  This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.<br /><br />



 </body>


Setting aside the fact that it doesn't work (which is covered in Bug 622539), we shouldn't be returning the html (which looks like the default response)
Assignee: nobody → tarek
The status code is still the right one, and those APIs are used by non human clients. So I don't think this is a problem.

I am closing this one about the 401 error, but feel free to open a new issue for the text/plain vs text/html on 4xx. This is an issue global to all our services in Python.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.