[ic] rewite rules killed images - and cookies

[Mike Heins]

Quoting Philip S. Hempel (pshempel@linuxhardcore.com):
> Mike Heins wrote:
> > Quoting Mike Heins (mike@perusion.com):
> > 
> >>Quoting Philip S. Hempel (pshempel@linuxhardcore.com):
> >>
> >>>Yes test and confirmed the settings that DB used and I also,
> >>>have seemed to create a proper cookie for this
> >>>configuration.
> >>>
> >>>But why is it still required to create this original cookie
> >>>that points to the CGI?
> >>
> >>It *isn't* necessary unless you have multiple catalogs
> >>on the same domain. If you do, though, you need it.
> > 
> > 
> > Actually, that is not true any more as of 4.8 -- you can
> > set different cookie names with CookieName on a per-catalog
> > basis.
> > 
> > (Correcting myself with something I had not followed all
> > the way through when I did it. I added CookieName for
> > another reason.)
> > 
> 
> My reading of the CookieName directive was
> very unclear, but clear enaough that I thought
> it was only used in pages that needed special
> cookies created.
> 
> I had thought originally this was the correct
> way to go. But finding no docs on it and
> looking through the list I was quite confused.
> 
> So cookiename would look like this...
> 
> "CookieName /"

No, it would be something like:

	CookieName   MV_OTHERCAT_SESSION_ID

It is the name of the cookie, not the path. It prevents
clashes with the MV_SESSION_ID from another catalog.

Can't get around MV_USERNAME and MV_PASSWORD yet, though.
Perhaps I ought to put in AutoCookieName, which would
do:

	my $catname = uc $Vend::CatalogName;
	$catname =~ s/\W+//g;
	for(qw/ CookieName UserCookieName PassCookieName /) {
		$Vend::Cfg->{$_} =~ s/^MV/$catname/;
	}

That would automatically prepend the catalog name to the
names of the cookies, and prevent problems.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting    http://www.perusion.com/
phone +1.513.523.7621      <mike@perusion.com>

Friends don't let friends use Outlook. -- Bob Blaylock