<?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>only small attachment uploads work over https</title> 
  <pubDate>Fri, 10 Apr 2026 18:27:18 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/11031</link> 
  <atom:link rel="self" type="application/rss+xml" title="only small attachment uploads work over https" href="https://bugs.horde.org/ticket/11031/rss" /> 
  <description>only small attachment uploads work over https</description> 
 
   
   
  <item> 
   <title>We&#039;re running both latest H4 and Horde 1.2.9 on SLES11SP1 Li</title> 
   <description>We&#039;re running both latest H4 and Horde 1.2.9 on SLES11SP1 Linux with Apache2, set up so that client-side certificates are required to access the Horde directories.

Both directories (installed in sibling directories) are set up identically in the httpd config file.

When uploading attachments to new emails in Horde 1.2.9, this works for all file sizes.

When uploading attachments in Horde4, this only works for small files (up to about 5.4 kB upload works, 5.5 kB and more stalls). With the larger files, the message &quot;Hochladen... (meindateiname)&quot; (&quot;Uploading... (theuploadsfilename)&quot;) remains forever.

Looking at the httpd access and error log, I see the following:

- Horde 1.2.9, any file size, just access log, no error log entry:
ourserver - /mycertDNgoes here [27/Feb/2012:12:14:53 +0100] &quot;POST /horde-webmail-1.2.9/dimp/compose.php HTTP/1.1&quot; 200 177 &quot;https://ourserver/horde-webmail-1.2.9/dimp/compose.php?type=new&quot; &quot;Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1&quot;

- Horde4, small file, just access log, no error log entry
ourserver - /mycertDNgoeshere [27/Feb/2012:12:13:25 +0100] &quot;POST /horde-webmail-4.0/services/ajax.php/imp/addAttachment HTTP/1.1&quot; 200 197 &quot;https://ourserver/horde-webmail-4.0/imp/compose-dimp.php?type=new&amp;ajaxui=1&amp;uniq=1330341182271&quot; &quot;Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1&quot;

- Horde4, file 5.5 kB or larger:
access log:
ourserver - /mycertDNgoeshere [27/Feb/2012:12:12:41 +0100] &quot;POST /horde-webmail-4.0/services/ajax.php/imp/addAttachment HTTP/1.1&quot; 200 - &quot;https://ourserver/horde-webmail-4.0/imp/compose-dimp.php?type=new&amp;ajaxui=1&amp;uniq=1330341126841&quot; &quot;Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1&quot;

error log:
[Mon Feb 27 12:12:41 2012] [error] [client ourclient] Re-negotiation handshake failed: Not accepted by client!?, referer: https://ourserver/horde-webmail-4.0/imp/compose-dimp.php?type=new&amp;ajaxui=1&amp;uniq=1330341126841

This might be related to some Apache configuration issue - but since 1.2.9 works like a charm and H4 doesn&#039;t, from the same client to the same server with identical configuration (except for directory names), I&#039;d at least like to know what&#039;s different between both mechanisms.

One could of course say: Switching to H4 breaks it. ;-)

PS: Just in case someone might as, despite it working in 1.2.9:

/etc/php5/apache2/php.ini:
upload_max_filesize = 200M
post_max_size = 256M

And setting &quot;LimitXMLRequestBody 0&quot; in the horde4-related section of httpd&#039;s config doesn&#039;t bring any change, either.</description> 
   <pubDate>Mon, 27 Feb 2012 12:34:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11031#t70501</link> 
  </item> 
   
  <item> 
   <title>This is not a Horde issue.  HTTP transfer details are handle</title> 
   <description>This is not a Horde issue.  HTTP transfer details are handled by the HTTP server, not Horde/PHP.</description> 
   <pubDate>Thu, 08 Mar 2012 09:17:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11031#t70643</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
