any obvious answer to an infinite 301 redirect with ring? I used the secure-site-defaults, on amazon elb.

@stvnmllr2 I'd use curl -I to debug it. That'll show exactly what Location: header is coming back, then request that via curl -I and you should have a good idea of what's going wrong.

thanks @seancorfield. Will try it. Not sure it helped. Just redirecting to itself, hence the infinite loop. Seems the request must not have the scheme passed in correctly to ring. Just a guess.

Guess I can add some debugging in somewhere.