>
> --
> 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 wrote:
>
>> I set https, but it never seemed to stick.
>>
>> Not sure if you
; VMware, Inc. - http://www.vmware.com
>
>
> On Sat, Jun 16, 2012 at 9:15 PM, Dan Dumont wrote:
>
>> SetEnv HTTPS on
>> In the apache config worked like a charm though.
>>
>> I did end up filing this issue
>> http://code.google.com/p/reviewboard/issu
SetEnv HTTPS on
In the apache config worked like a charm though.
I did end up filing this issue
http://code.google.com/p/reviewboard/issues/detail?id=2639
I'm not sure yet if this will cause problems now that I've solved the
redirect https issues.
On Sat, Jun 16, 2012 at 11:56 PM,
at the the border.
Would be nice if you guys could just return protocol relative urls
//reviewboard.apache.org/etc...
Any advice on where to stick that config setting to force https urls?
On Saturday, June 16, 2012 11:16:27 PM UTC-4, Dan Dumont wrote:
>
> Request URL:
> https://review
. status: "pending"
10. summary: ""
11. target_groups: []
12. target_people: []
13. testing_done: ""
14. time_added: "2012-06-17 02:58:19"
2. stat: "ok"
Is there a setting I'm missing that controls the protocol?
Do you use a protocol
relative url? //reviews.apache.org/path/to/api
or do you build it off of some variable in the config?
On Saturday, June 16, 2012 9:37:11 PM UTC-4, Dan Dumont wrote:
>
> Didn't touch the apache config.
> It's a http -> https redirect (no ide
he configuration at
> all, or is that all the same from before?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Sat, Jun 16, 2012 at 4:53 PM, Dan Dumont wrote:
Hi Christian,
I got things mostly up and running again by reconstructing the sql tables
in a new 1.5.5 install and then upgrading that.
Having some difficulty at the site though. Many different api problems it
looks like.
I can't publish drafts, getting a 301:
OPTIONS /api/review-requests/53
