3119: Error publishing draft

pian*****@gmai***** (Google Code) (Is this you? Claim this profile.)
Dec. 9, 2013
3085 
What version are you running?
1.7.16

What's the URL of the page containing the problem?
https://rb.myproject.com/r/12/#

What steps will reproduce the problem?
1. Edit draft, setfields values (minimal)
2. Try to publish
3. Error occurred

What is the expected output? What do you see instead?
Expected: published review. Received error...

Error Code: 0
Error Text: error
Request URL: http://rb.myproject.com/api/review-requests/12/last-update/
Request Data: (none)



What operating system are you using? What browser?
Firefox/Chrome — both (Ubuntu)
On server: nginx + rb-site as fastcgi


Please provide any additional information below.

nginx config part:
        location /
        {
                fastcgi_pass 127.0.0.1:3033;
                fastcgi_param PATH_INFO $fastcgi_script_name;
                fastcgi_param REQUEST_METHOD $request_method;
                fastcgi_param QUERY_STRING $query_string;
                fastcgi_param CONTENT_TYPE $content_type;
                fastcgi_param CONTENT_LENGTH $content_length;
                fastcgi_pass_header Authorization;
                fastcgi_intercept_errors off;
        }
david
#1 david 
Is there anything in the nginx or reviewboard logs?

Generally, wsgi works much better than fastcgi for deploying python applications.
  • +NeedInfo
#2 pia****@mx1*** (Google Code) (Is this you? Claim this profile.) 
There is no difference between fastcgi and wsgi. There were some errors in nginx log, but fixing them did not change anything. I forgot some headers:

                fastcgi_param SERVER_ADDR $server_addr;
                fastcgi_param SERVER_PORT $server_port;
                fastcgi_param SERVER_NAME $server_name;
                fastcgi_param SERVER_PROTOCOL $server_protocol;

But the problem with publishing review is not solved.

nginx logs are empty.
application log in debug mode is also empty.

No request is sent to server. See my attachement, it is a client-side bug, request is not sent anyware, stays inpending state:

Request URL:http://rb.example.com/api/review-requests/9/draft/
Request Headersview parsed
OPTIONS http://rb.example.com/api/review-requests/9/draft/ HTTP/1.1
Access-Control-Request-Method: PUT
Origin: https://rb.example.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/28.0.1500.71 Chrome/28.0.1500.71 Safari/537.36
Access-Control-Request-Headers: accept, origin, content-type
#4 pia****@mx1*** (Google Code) (Is this you? Claim this profile.) 
Found a problem.

OPTIONS http://rb.example.com/api/review-requests/9/draft/ HTTP/1.1

Should be https
#5 pia****@mx1*** (Google Code) (Is this you? Claim this profile.) 
Found the same bug:

http://code.google.com/p/reviewboard/issues/detail?id=3085
#6 pia****@mx1*** (Google Code) (Is this you? Claim this profile.) 
For everyone who has the same problem. We should pass HTTPS fastcgi param:
fastcgi_param HTTPS $https;

The problem has very simple solution.
david
#7 david