| Summary | Cookie-Domain will be set with leading dot |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | horde_mailing (at) der-domi (dot) de |
| Created | 02/25/2018 (2938 days ago) |
| Due | |
| Updated | 02/26/2018 (2937 days ago) |
| Assigned | |
| Resolved | 02/26/2018 (2937 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
coockies. But it was some configuration issue which I can't reproduce.
But now it works again.
State ⇒ Not A Bug
Priority ⇒ 1. Low
Please use the mailing lists to ask for support.
http://www.horde.org/mail/ contains a list of all available mailing lists.
I see that some domains set coockies indeed with a leading domain. For
domains something like "domain.com". But not for "www.domain.com".
Can you please check it? Thanks!
to my environment ($conf['cookie']['path'] = '/path';)
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Cookie-Domain will be set with leading dot
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
.\base\config\conf.php.dist as template. But if I access Horde via
browser I will get an empty page.
I saw that Firefox (Win10) had set a cookie for the installation. But
the cookie-domain starts with a dot. This seems to be an issue and
shall be fixed.