211: Error when saving draft created by post-review

data****@gmai***** (Google Code) (Is this you? Claim this profile.)
chipx86
chipx86
Oct. 12, 2007
What's the URL of the page containing the problem?
It's an internal server

What steps will reproduce the problem?
1. Change a file and create the diff using post-review (the checked out
files should not be on the server).
2. Edit the review request on the same machine and try to save changes.
3. You will get the following error:
Error:
Saving the draft has failed due to a server error:communication failure.
Please try again later. If this continues to happen, please report it to
your administrator

What is the expected output? What do you see instead?
This works perfectly if run from the server.

What operating system are you using? What browser?
Server: Linux (Ubuntu)
Client: Windoze Firefox 2.0


Please provide any additional information below.

Reviewboard is the latest checkout as of Aug 22.
#1 data****@gmai***** (Google Code) (Is this you? Claim this profile.)
One thing I forgot to mention was that the data actually does get saved even though
it complains that the draft could not be saved - it's just that the browser reports
an error...
chipx86
#2 chipx86
I've seen this, but it's in no way related to post-review. Is this 100% reproduceable
for you?

Looking through the YUI code (which generates this error), it looks like one cause is
due to going through a corporate proxy. You might want to make sure there's an
exception for your internal reviewboard server in your proxy settings, if you have one.
  • +chipx86
#3 data****@gmai***** (Google Code) (Is this you? Claim this profile.)
Hmmm. I have to investigate this a little further. This is 100% reproducible. My
server is running on a Linux VM on VMWare. The actual server is on the same VLAN as
my PC. I'll try to use the VM server itself and see if it is a problem on our VLAN
switch or the VM itself...
david
#4 david
Can you try accessing it without a proxy?
  • +NeedInfo
david
#5 david
Assuming this is fixed for you.  If not, please reopen the bug.
  • -NeedInfo
    +Fixed