Why does AppHarbor + RequireHttpsAttribute equal frowny-face :(
Asked Answered
C

1

9

First deployment to AppHarbor today. After some initial work getting it to build, I successfully deployed an MVC3 app.

There is a problem with using the RequireHttpsAttribute though. I noticed at first that http pages were working fine, but https pages were getting the error that the web page has a redirect loop.

I have been meaning to require https for the entire app, so I went and added a global RequireHttpsAttribute filter in global.asax. Now every single page is getting the redirect loop error, in chrome and FF.

Assume this has something to do with port redirecting behind the scenes. How to fix it? Do I need a custom RequireHttpsAttribute?

Christiansand answered 23/1, 2012 at 18:28 Comment(1)
I didn't know that the problem is caused by requirehttpsattribute, I just got an endless redirect 302 loop. Firefox said the problem may be caused by cookie, which led me to the wrong direction. Fortunately I had an idea to browse the appharbor tag and found this post. Thanks!Forlini
C
9

Found the answers here and here. A custom RequireHttpsAttribute override was necessary.

Christiansand answered 23/1, 2012 at 19:13 Comment(1)
Another option here: #11510537Nappie

© 2022 - 2024 — McMap. All rights reserved.