Re: MidCOM indexer - navi issue
Torben Nehmer <[email protected]>
| Newsgroups | gmane.comp.web.midgard.user |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Henri Bergius wrote: > | You should use MIDCOM_NAV_FULLURL instead. If you switched to this > | alredy, tell me and I'll check if that member is possibly populated wrong. > > I know I should switch to that. However, FULLURL gives the full URL > (http://www.example.com/path/to/topic) whereas only the path > (/path/to/topic) would be better option as FULLURL won't IIRC > handle port 0 properly. NAP will always check against the port of the current Virtual Host ($_SERVER['SERVER_PORT']), so it doesn't interfere with Midgard Port-0 items. Of course, if you have the same site active at several ports (say HTTP and HTTPS) then you will might run into problems with the NAP cache. Anywaya, could you please elaborate your considerations above? Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:[email protected] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCa3SGJPh4Kn6d5FYRAqnZAKDiwzwkvVhetS8O7BA+N6ti078+LQCg4JO/ 64MdG6uwZrZVQtY4joQ8iR8= =UOgA -----END PGP SIGNATURE-----