Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 3868 by Unable publish code review

*** You must complete this form in its entirety, or your bug report will be
*** rejected.
*** If you have a security issue to report, please send it confidentially
*** Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
*** For customer support, please post to
*** If you have a patch, please submit it to
*** This bug tracker is public. Please check that any logs or other
*** that you include has been stripped of confidential information.

What version are you running?

What's the URL of the page containing the problem?

What steps will reproduce the problem?
1. Open any CR link
2. Try to publish any CR or Review any CR.
3. I get the error attached below

What is the expected output? What do you see instead?

CR should get published to assigned person.

What operating system are you using? What browser?

OS - Mac OS X - Yesomite. Chrome.

Please provide any additional information below.
I getting the following error:
Error Code: 401

Error Text: Unauthorized

Request URL: /api/review-requests/3672687/

Request Data: (none)

Response Data:

There may be useful error details below. The following error page may be useful to your system administrator or when reporting a bug. To save the page, right-click the error below and choose "Save Page As," if available, or "View Source" and save the result as a .html file.

Warning: Be sure to remove any sensitive material that may exist in the error page before reporting a bug!


        Screen Shot 2015-05-11 at 3.36.53 pm.png  76.0 KB

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to