nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

login cookie & domains..

nipper

OK, so if I log into my server with:

http://server/iw/

& then log in with

http://server.myco.com/iw/

the cookie does not recognize my login

Yes it seems like a nit, however, if i embed my URL in a JSP or email
(http://server.myco.com/iw/task....) but log in with the other URL it requires
a login.

So my users complain (they whine like Smitty). I am pushing everyone to
update their bookmarks, but curious if there is any other option.

TS 552, Solaris 2.8

Andy

Find more posts tagged with

Comments

Migrateduser

There is some way to configure Apache to redirect to the FQDN if a user comes over IP or hostname. Put code something like this towards the top of rewrite.conf.template. Not sure how you get this rebuilt into rewrite.conf. You should check apache docs for specifics.

RewriteCond %{HTTP_HOST} !^hostmname\.domain\.com [NC]
RewriteRule ^/(.*)$ http://hostname.domain.com/$1 [L,R]

Edited by john on 08/11/04 09:14 AM (server time).

Dwayne

Well, cookies are always stored on the local user's machine with the domain that sent them. It's a security feature to keep those cookies separate - I don't think you can attack it from that side.

You might be able to look at the apache config files, and force a redirect to the FQDN form of the URL if users come in with just the hostname portion. Look at rewrite.conf (well, rewrite.conf.template)

--

Current project: TS 5.5.2/6.1 W2K