I'm currently republishing a site that's been migrated from 5.2 to 2011 SP1 HR1.

The main change is that we're now using HTTPS publishing.

However, this has now raised an issue whereby some pages are now failing with the following error in during the Transport phase.

Transport failed: Could not transport tcm_[tcmid].Content.zip using HTTPS, cause: Internal Server Error

Looking at the server logs, the HTTPS publisher website is throwing the following error (cut down for ease of viewing):

Event Code: 3004 Event Message: Post size exceeded allowed limits

On a normal .Net application, I would update the maxRequestLength value of the httpRuntime element in the web.config

eg <httpRuntime maxRequestLength="102400" executionTimeout="300"/>

However as the HTTPS publisher doesn't have a web.config, I'm unsure where I'd need to make that change.

I have updated the MaxSize property of the HTTPSReceiver element of the cd_deployer_conf.xml and restarted the service which fixed a 'Request Entity Too Large' issue I was also having, but has not solved this issue.

Any help gratefully received.

1 Answer 1


You may have to create a web.config file in the root of the HTTPUpload web application. Here is an example web.config that I've used in the past:

PLEASE NOTE: One of these values is in kilobytes, and the other in bytes - Pesky Microsoft!

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">         
        <!-- This value is in **kilobytes** -->
        <!-- 512000 kilobytes = 500MB -->
        <httpRuntime executionTimeout="1200" maxRequestLength="512000" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100"/>

            <!-- This is the value in **bytes** -->
            <!-- 524288000 bytes = 500MB -->
            <!-- The maximum for this is 4,294,967,295 (3.99GB) - http://stackoverflow.com/questions/4022434/-->
            <requestLimits maxAllowedContentLength="524288000" />

You may have to increase the HTTPSReceiver value in the deployer config too:

<HTTPSReceiver MaxSize="524288000" Location="D:\tridion\incoming" InProcessDeploy="true"/>
  • 1
    Cheers mate - works a treat. Is this the Tridion supported solution or just something you've done to get it to work in the past? Commented Mar 8, 2013 at 17:14
  • Thanks for confirming that it works. Yes, I think that this is the solution that Tridion Support recommend. It was certainly the recognised solution on the Tridion forums back in the day. Commented Mar 8, 2013 at 17:22
  • 1
    Just spotted that this is actually listed as the tip of the month in this month's newsletter that arrived in my inbox today. Spooky! Commented Mar 8, 2013 at 17:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.