alain.deurveilher@... wrote:
>Hi list,
>
>Some poeple encounter the following problem with their browser, with the
>cookies.
>
>They cannot log in mantis with the host name in the adress, like :
>http://hostname/mantis/login_page.php
>
>an error occurs when they submit login : something like "your browser does
>not accept cookies, ..."
>
>but when they put the IP address :
>http://serverIPaddress/mantis/login_page.php
>
>and submit, they can be logged in mantis.
>
>Does somebody know where it come from, and how to solve the pb ?
>
>(some information : cookies acceptance are set in the browser configuration
>| browser is IE, version 6 | OS win2K, winNT, winXP)
>
>Thanks a lot.
>
>--
>AlaiN.
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: SourceForge.net Broadband
>Sign-up now for SourceForge Broadband and get the fastest
>6.0/768 connection for only $19.95/mo for the first 3 months!
>http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
>_______________________________________________
>Mantisbt-help mailing list
>Mantisbt-help@...
>https://lists.sourceforge.net/lists/listinfo/mantisbt-help
>
>
There is a Cookie specification :
=========================================================================
Excerpt from RFC 1035
2.3.1 Preferred name syntax
The DNS specifications attempt to be as general as possible in the rules
for constructing domain names. The idea is that the name of any
existing object can be expressed as a domain name with minimal changes.
However, when assigning a domain name for an object, the prudent user
will select a name which satisfies both the rules of the domain system
and any existing rules for the object, whether these rules are published
or implied by existing programs.
For example, when naming a mail domain, the user should satisfy both the
rules of this memo and those in RFC-822. When creating a new host name,
the old rules for HOSTS.TXT should be followed. This avoids problems
when old software is converted to use domain names.
The following syntax will result in fewer problems with many
applications that use domain names (e.g., mail, TELNET).
domain <http://penelope.gruppotesi.com/cgi-bin/domain> ::= subdomain <http://penelope.gruppotesi.com/cgi-bin/subdomain> | " "
subdomain <http://penelope.gruppotesi.com/cgi-bin/subdomain> ::= label <http://penelope.gruppotesi.com/cgi-bin/label> | subdomain <http://penelope.gruppotesi.com/cgi-bin/subdomain> "." label <http://penelope.gruppotesi.com/cgi-bin/label>
label <http://penelope.gruppotesi.com/cgi-bin/label> ::= letter <http://penelope.gruppotesi.com/cgi-bin/letter> [ [ ldh-str <http://penelope.gruppotesi.com/cgi-bin/ldh-str> ] let-dig <http://penelope.gruppotesi.com/cgi-bin/let-dig> ]
ldh-str <http://penelope.gruppotesi.com/cgi-bin/ldh-str> ::= let-dig-hyp <http://penelope.gruppotesi.com/cgi-bin/let-dig-hyp> | let-dig-hyp <http://penelope.gruppotesi.com/cgi-bin/let-dig-hyp> ldh-str <http://penelope.gruppotesi.com/cgi-bin/ldh-str>
let-dig-hyp <http://penelope.gruppotesi.com/cgi-bin/let-dig-hyp> ::= let-dig <http://penelope.gruppotesi.com/cgi-bin/let-dig> | "-"
let-dig <http://penelope.gruppotesi.com/cgi-bin/let-dig> ::= letter <http://penelope.gruppotesi.com/cgi-bin/letter> | digit <http://penelope.gruppotesi.com/cgi-bin/digit>
letter <http://penelope.gruppotesi.com/cgi-bin/letter> ::= any one of the 52 alphabetic characters A through Z in
upper case and a through z in lower case
digit <http://penelope.gruppotesi.com/cgi-bin/digit> ::= any one of the ten digits 0 through 9
Note that while upper and lower case letters are allowed in domain
names, no significance is attached to the case. That is, two names with
the same spelling but different case are to be treated as if identical.
The labels must follow the rules for ARPANET host names. They must
start with a letter, end with a letter or digit, and have as interior
characters only letters, digits, and hyphen. There are also some
restrictions on the length. Labels must be 63 characters or less.
================================================================================
If you use a domain name: xxx.yourdomain.ccc the cookie is setted OK.
I think a better explanation is in the PHP documentation
(http://it2.php.net/manual/en/function.setcookie.php)
I've experience this problem with another PHP product (phptrouble ticket)
As a workaround in my test installation on Windows I've configured my
hosts file in this way:
127.0.0.1 localhost http://www.fakedomain.net
|
