Ah, that makes sense.
Was that the only option you needed then? It'd be nice to have some docs on
this somewhere.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Jun 18, 2012 at 4:51 AM, Dan Dumont
Yes. And I agree. :)
- sent from my Galaxy Nexus Android phone.
On Jun 18, 2012 3:23 PM, Christian Hammond chip...@chipx86.com wrote:
Ah, that makes sense.
Was that the only option you needed then? It'd be nice to have some docs
on this somewhere.
Christian
--
Christian Hammond -
Didn't touch the apache config.
It's a http - https redirect (no idea why the browser isn't simply
following it, do ajax requests eat the 301 errors? I can't remember).
This is a brand new draft.
On Saturday, June 16, 2012 9:31:26 PM UTC-4, Christian Hammond wrote:
Hi Dan,
It looks like
Ahh ok. So a bit more info:
http://stackoverflow.com/questions/228225/prevent-redirection-of-xmlhttprequest
If the origin of the URL conveyed by the Location header is same
origin with the XMLHttpRequest origin and the redirect does not
violate infinite loop precautions, transparently
Request URL:
https://reviews.apache.org/api/review-requests/5345/?api_format=json
responds:
1. review_request: {status:pending, last_updated:2012-06-17 02:58:20,
description:,…}
1. branch:
2. bugs_closed: []
3. changenum: null
4. description:
5. id: 5345
I found
https://groups.google.com/forum/?fromgroups#!topic/reviewboard/yIOamU1uvIY
But I tried setting
os.environ['HTTPS'] = on
In the reviewboard.wsgi file, but no dice. I'm pretty sure we have a
reverse proxy of some sort in front of us terminating SSL at the the border.
Would be nice
Hi,
Deleted that column, and a few more that came up, then got stuck at this
one:
Evolution could not be simulated, possibly due to raw SQL mutations
Error: Error applying evolution: (1091, Can't DROP 'name'; check that
column/key exists)
Regarding exactly what I did, cant say exactly, but I
Your upgrade apparently also upgraded to Review Board 1.6.7, which has many
significant changes. And that upgrade failed, because of the django_session
issue.
I've seen that django_session error before. Not sure what the cause is, but
basically, that's a database index that was created, and
On Sunday, June 10, 2012 1:04:30 PM UTC+9:30, Christian Hammond wrote:
Your upgrade apparently also upgraded to Review Board 1.6.7, which has
many significant changes. And that upgrade failed, because of the
django_session issue.
I've seen that django_session error before. Not sure what
No, that should never have been reached. That shows you're in some
half-modified database state, which shouldn't have happened, given that
database transactions are used during the evolution and the earlier error
should have prevented the other modifications.
At this point, I really wish you had
10 matches
Mail list logo
