[an error occurred while processing the directive]

	cosign-discuss at umich.edu
	general discussion of cosign development and deployment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in IIS Cosign 1.1.1?

To: Brett Lomas <b.lomas@xxxxxxxxxxxxxx>
Subject: Re: Bug in IIS Cosign 1.1.1?
From: Jarod <jarod@xxxxxxxxx>
Date: Thu, 10 Mar 2005 02:00:38 -0500 (EST)
Cc: cosign-discuss@xxxxxxxxx
In-reply-to: <20050310035025.264543490F@smtpd.itss.auckland.ac.nz>
References: <20050310035025.264543490F@smtpd.itss.auckland.ac.nz>

I think the szProtocol in SetCookieAndRedirect needs to be 6 bytes, given
you are copying in "https" in most cases.

Wow, sorry, I must've had a brain lapse when adding up that magic number in my head.

Also, when I compile the IIS Cosign module with debugging (the debug
configuration) and install it and attempt to access a protected area I
messages on the server like the pic attached. I have looked into a little,
but cannot find why this happening.

It's possible that the szProtocol is causing this since it's 'near' szUrl in the stack. I'll double check my bounds checking in that part of the code -- SetCookieAndRedirect.

--Jarod

References:
- Bug in IIS Cosign 1.1.1?
  - From: Brett Lomas

Prev by Date: Cosign Filter creates unparsable URL on post
Next by Date: Re: Problems adding the IIS filter
Previous by thread: Bug in IIS Cosign 1.1.1?
Next by thread: Cosign Filter creates unparsable URL on post
Index(es):
- Date
- Thread

[an error occurred while processing the directive]