Skip to Content.
Sympa Menu

shibboleth-dev - RE: Proposed (draft) Webserver API

Subject: Shibboleth Developers

List archive

RE: Proposed (draft) Webserver API


Chronological Thread 
  • From: "Scott Cantor" <>
  • To: "'Derek Atkins'" <>
  • Cc: <>
  • Subject: RE: Proposed (draft) Webserver API
  • Date: Thu, 2 Dec 2004 10:33:10 -0500
  • Organization: The Ohio State University

> True. Are you suggesting that we store a callback state object in
> some special data of the apache request_rec structure?

No, in the callback object you were creating. I'm just noting that I added
some state to the SHIRE object so that I could cache some things like
manufacturing the SHIRE location, and we could just add the Apache/IIS
"state" structure your callback was storing to what I had, and it seems like
it's useful to push the two together.

> The only two data I think I need access to (besides the htaccess) is
> the key used to detect whether to run the shib_post_handler on apache2
> and the authtype for basicHijack. I can probably work around these
> two if I think about it harder.

You could just abstract some of the auth type handling so that it can be
stubbed out on IIS, since there's no real equivalent.

> Yes, I know. I didn't want to use this API for actual debugging
> information, only actual failure information. All the debugging

Ok.

> Hmm, so basically you think something like this:
>
> void* sendPage(String msg, pair<String,String> headers[] =
> null, int code = 200);

Yeah, that's roughly similar to the functions I created in the IIS module.

-- Scott




Archive powered by MHonArc 2.6.16.

Top of Page