On Mon, Jun 12, 2017 at 6:18 PM, sebb <seb...@gmail.com> wrote:
> On 12 June 2017 at 23:04, Sam Ruby <ru...@intertwingly.net> wrote:
>> On Mon, Jun 12, 2017 at 5:38 PM, sebb <seb...@gmail.com> wrote:
>>> I tried testing /roster/committer/__self__ on my local installation.
>>>
>>> However it redirects to https: which I don't have set up.
>>>
>>> It seems strange that the redirect should change the protocol.
>>
>> Indeed, that would be strange.
>>
>> It doesn't redirect to https: on either my Mac or Ubuntu machines,
>> neither of which have https://whimsy.local/ set up.
>>
>> The source also uses a relative URL:
>>
>> https://github.com/apache/whimsy/blob/master/www/roster/main.rb#L89
>>
>> Here is the relevant curl output on my machine (in this case, MacOSX):
>>
>> $ curl --head --user rubys http://whimsy.local/roster/committer/__self__
>> Enter host password for user 'rubys':
>> HTTP/1.1 303 See Other
>> Date: Mon, 12 Jun 2017 22:01:06 GMT
>> Server: Apache/2.4.25 (Unix) Phusion_Passenger/5.1.3
>> Vary: Accept-Encoding
>> X-XSS-Protection: 1; mode=block
>> X-Content-Type-Options: nosniff
>> X-Frame-Options: SAMEORIGIN
>> X-Powered-By: Phusion Passenger 5.1.3
>> Location: http://whimsy.local/roster/committer/rubys
>> Status: 303 See Other
>> Content-Type: text/html;charset=utf-8
>
> I get
>
> HTTP/1.1 303 See Other
> Date: Mon, 12 Jun 2017 22:11:42 GMT
> Server: Apache/2.4.25 (Unix) Phusion_Passenger/5.1.2
> Vary: Accept-Encoding
> X-XSS-Protection: 1; mode=block
> X-Content-Type-Options: nosniff
> X-Frame-Options: SAMEORIGIN
> X-Powered-By: Phusion Passenger 5.1.2
> Location: https://my.whimsy/roster/committer/sebb
> Status: 303 See Other
> Content-Type: text/html;charset=utf-8
>
> Also MacOSX.
>
> (a bit later)
> I've discovered the problem: I had 'SetEnv HTTPS on' in the httpd.conf
> Not sure why...

You may not have the latest httpd.conf.  See:

https://github.com/apache/whimsy/blob/master/tools/mkconf.rb#L17

Also:

https://github.com/apache/whimsy/commit/4d85c0994596f1eb3be5ec272997020005894a2d

- Sam Ruby

Reply via email to