# Cannot DELETE document from DELL ECS via HAproxy

**URL:** <https://discourse.haproxy.org/t/cannot-delete-document-from-dell-ecs-via-haproxy/9129>\
**Category:** Help!\
**Created:** [October 17, 2023, 1:34pm UTC](https://discourse.haproxy.org/t/cannot-delete-document-from-dell-ecs-via-haproxy/9129 "2023-10-17T13:34:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![benarson](https://avatars.discourse-cdn.com/v4/letter/b/9de0a6/32.png) [@benarson](https://discourse.haproxy.org/u/benarson)\
**Post date:** [October 17, 2023, 1:34pm UTC](https://discourse.haproxy.org/t/cannot-delete-document-from-dell-ecs-via-haproxy/9129/1 "2023-10-17T13:34:08Z")

</div>

Hello,  
I am running **HAProxy version 2.7.2**  
I have access to DELL ECS via HAproxy.  
I am using **IBM Filenet** application to connect to the ECS.  
When I connect to the ECS directly, there is no issue.  
When I configure IBM Filenet using HAproxy, I can only READ/WRITE documents from/to DELL ECS,  
but **cannot DELETE document** from ECS.

## Here below is the error I got on Filenet when trying to DELETE a document: n_ested exception is: javax.ejb.EJBTransactionRolledbackException: nested exception is: javax.ejb.EJBException: See nested exception; nested exception is: com.filenet.api.exception.EngineRuntimeException: FNRCC0091E: CONTENT\_FCP\_GET\_RETENTION\_PERIOD\_FAILED: The retention period for the content element could not be retrieved for this provider. Device Id: [{0CFB11E1-0037-48F3-A079-2CCBE5025215}]; Device Name: [FCD\_AWS\_S3\_INT1]; Root Cause [FNRCC0255: Unexpected missing response header Content-Length for storage device {1}.]_

And from the haproxy.log:  
_Oct 17 12:35:35 localhost haproxy[34684]: 10.x.x.x:44695 [17/Oct/2023:12:35:35.491] https-in~ s3\_backend/pecsdata01 0/0/0/142/142 200 416 - - ---- 5/1/0/0/0 0/0 “HEAD /filenet-prod-s3/51C3D452-9128-4216-BA7D-35414904DB88-0?versionId=null HTTP/1.1”_

**Here below is my HAProxy configuration:**  
frontend http-in  
bind \*:80 name http  
default\_backend s3\_backend  
# Define the hostnames  
acl host\_s3 hdr(host) -i -m dom ecsproxy.mydomain  
acl host\_s3\_ip hdr(host) -i -m dom 10.x.x.x  
# Route to backend  
use\_backend s3\_backend if host\_s3  
use\_backend s3\_backend if host\_s3\_ip

frontend https-in  
bind \*:443 name https ssl crt /etc/haproxy/ecsproxy.mydomain.pem  
http-request add-header X-Proto https if { ssl\_fc }  
# Define the hostnames  
acl host\_s3 hdr(host) -i -m dom ecsproxy.mydomain  
acl host\_s3\_ip hdr(host) -i -m dom 10.x.x.x  
# Route to backend  
use\_backend s3\_backend if host\_s3  
use\_backend s3\_backend if host\_s3\_ip

backend s3\_backend  
option httpchk  
http-check connect  
http-check send meth GET uri /?ping ver HTTP/1.1 hdr Host ecsproxy.mydomain  
http-check expect status 200-399  
# List of data nodes. S3 runs on port 9020.  
server pecsdata01 10.x.x.1:9020 check  
server pecsdata02 10.x.x.2:9020 check  
server pecsdata03 10.x.x.3:9020 check  
server pecsdata04 10.x.x.4:9020 check  
server pecsdata05 10.x.x.5:9020 check  
server pecsdata06 10.x.x.6:9020 check

Is there onyone who can help how to fix this issue?  
Any help would be appreciated.

B.