Support

Akeeba Backup for Joomla!

#35564 API Error bad_request: Missing header: Content-Length

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by on Saturday, 28 August 2021 20:17 CDT

[email protected]

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!


EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.


Description of my issue:

Hello,

We are using post processing to upload our backup to Backblaze.  The backup SUCEEDS, but, we get these warnings: can I make them go away?

Failed to upload kickstart.php
Error received from the post-processing engine:
Backblaze B2 API Error bad_request: Missing header: Content-Length

 

Thanks!

Pat

nicholas
Akeeba Staff
Manager

There are two distinct problems which may result in the same error.

BackBlaze B2 does not have a centralised API server. Instead, whenever you are running a backup the centralised API server gives us an endpoint URL to the B2 pod (the actual server in their datacenter which stores your files) which hosts its own API server. Sometimes a specific pod may be running a buggy version of the B2 API server, causing an issue like that to appear even though we are sending the Content-Length header correctly.

The other problem has to do with your server. In some cases there is a proxy between your server and the rest of the Internet. Normally, proxies are transparent. However, in some cases a misconfigured proxy may alter or drop HTTP headers. If the proxy drops the Content-Length header you will get an error since this is required by B2.

I would recommend first trying to run your backup again or, alternatively, use the Manage Backups page to try and re-upload your backup archive to BackBlaze B2. Every time you run a backup or try to reupload you are getting to talk to a different B2 pod. This would solve the first problem.

If this doesn't work after trying it at least twice the problem must be a proxy in front of your server. This is something only your host can help you with. They are in control of their infrastructure. Let them know that their proxy is dropping or altering the HTTP Content-Length header which causes problems when uploading to BackBlaze B2. They should be able to reconfigure their proxy not to do that.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!