# X\_FORWARDED\_PROTO issues

**URL:** <https://www.ruby-forum.com/t/x-forwarded-proto-issues/133689>\
**Category:** Mongrel\
**Created:** [April 2, 2008, 5:18pm UTC](https://www.ruby-forum.com/t/x-forwarded-proto-issues/133689 "2008-04-02T17:18:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![evronm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/f1d935/32.png) [@evronm](https://www.ruby-forum.com/u/evronm)\
**Post date:** [April 2, 2008, 5:18pm UTC](https://www.ruby-forum.com/t/x-forwarded-proto-issues/133689/1 "2008-04-02T17:18:23Z")

</div>

Hi all -

I’m having some behavior that i can’t track down and I’m not sure if  
this is an Apache problem, a mongrel problem or neither.

Anyway - in my production setting I have two Apache 2.2 proxy servers  
pointing to two servers running mongrel instances.

In my SSL.conf file I have this:

RequestHeader set X\_FORWARDED\_PROTO ‘https’

It seems that if I reboot apache or reboot the mongrel instances  
without rebooting both in sequence that this proto value gets  
corrupted and request.ssl? in rails stops working properly. It’s as  
if request.ssl? is coming in incorrectly.

Just wondering if anyone has seen this behavior before.

THanks  
Mike