<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Configuration doesn&#039;t warn about non-alphanumerics in session name.</title> 
  <pubDate>Fri, 10 Apr 2026 11:23:07 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8531</link> 
  <atom:link rel="self" type="application/rss+xml" title="Configuration doesn&#039;t warn about non-alphanumerics in session name." href="https://bugs.horde.org/ticket/8531/rss" /> 
  <description>Configuration doesn&#039;t warn about non-alphanumerics in session name.</description> 
 
   
   
  <item> 
   <title>Apparently, when configuring a 3.3.4 Horde install, using a </title> 
   <description>Apparently, when configuring a 3.3.4 Horde install, using a session name of &quot;Horde-3.3.4&quot; causes problems with PHP (because of non-alphanumerics in the session name), which then causes all attempts to log in to be quietly verified, then dropped.  There is no apparent warning that this is happening, and no apparent subsequent diagnostics during those failed login attempts.



It might be useful for the configuration to either warn the user about non-alphanumerics in the session name, or just reject such names outright.



Switching to the session name of &quot;Horde334&quot; caused logins to start working again.</description> 
   <pubDate>Thu, 27 Aug 2009 10:56:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8531#t55561</link> 
  </item> 
   
  <item> 
   <title>There already is a description in the interface saying exact</title> 
   <description>There already is a description in the interface saying exactly this.</description> 
   <pubDate>Sun, 30 Aug 2009 12:17:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8531#t55588</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
