On Apr 1, 2009, at 4:49 PM, Chris Lafty wrote: > What a glorious day - I set up another web server on a separate box > and > after using my certificate authority to sign a self certificate, > doing a > couple of c_rehashes and and openssl -connect I got cosign to work, > somewhat. I will say that trying to test a cosign protected web > server > on the cosign log on server was problematic. Also, It's easier not > to > use the same certs to protect apache as you do cosign (for testing > purposes). I still have one issue. When I go to my protected url and > get bounced to my cosign log on server, for some reason the the URL I > get directed back to is malformed (https://cosigntest.stlawu.edu:80/test > ). > > https://lafty-rhel5.stlawu.local/cosign-bin/cosign.cgi?cosign-cosigntest.stlawu.edu=3c6Zo64N8MmCyu-IAIj78OKKnXtMp5rF1U+IWqrRkBalce9VRZ7dOWAALEL2TtUDYavq34Bd0nu7QTatgvWMuha-MRHoMWN9WVkH-8RRTkABVPrMQOJlMyG21ptZ;&https://cosigntest.stlawu.edu:80/test/ > > I'm using CosignHttpOnly Off, so I don't know where the port 80 is > coming from. My cosign test server does not listen on port 80. Any > idea? Something in the cosign.conf file?
Try setting CosignNoAppendRedirectPort to On. andrew ------------------------------------------------------------------------------ _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
