New Zenner
- Join Date:
- Feb 2012
- Posts:
- 70
- Plugin Contributions:
- 0
Downloads Fail because Error 346 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_LENGTH):
I've set up a Zen Cart store offering downloaded products only. Failure for customers to actually download their product is a showstopper of the first order. Immediately after their purchase or when they log into My Account > View > Download they are presented with an error page that states:
"Duplicate headers received from server
The response from the server contained duplicate headers. This problem is generally the result of a misconfigured website or proxy. Only the website or proxy administrator can fix this issue.
Error 346 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_LENGTH): Multiple distinct Content-Length headers received. This is disallowed to protect against HTTP response splitting attacks."
After two days of going back and forth with my ISP, performing web searches, and searching these forums I'm resorting to posting this problem because it's similar to other posts but also unique. My ISP techie researched my problem and responded:
Hello Yourvirtualworld,
Thank you for your patience.
I have checked once again the issue with the downloading the zip file at http://www.xxxxxxx.xxx . However, I have noticed that when we click on the download option the URL is re-directing to 'www.xxxxxxxx.xxx/pub/.zzychircojejjs/xxxxxxxxxxxxx.zip' (my masking for this forum) and displays the Bad Request error. This is because of the special character in the URL that is folder name with dot '.zzychircojejjs'. I have tried by renaming the folder without dot, however when I click on the download link it will create the separate folder name with dot inside the folder 'pub'. So, you need to check the script so that folder should appear without special character in the URL. If the issue still persists please contact the web developer or application vender regarding this issue.
If you have any further questions, please update the Support Console.
Sincerely,
Aldo XXXXX
Level 3 Technical Support:clap:
My question then is in three parts:
- What script must I modify to be rid of this error assuming Aldo's analysis is correct?
- What may have modified this script from its installed state to render it now buggy?
- If the script was not modified from the installed version 1.3.9H then how could it ship to users and cause days of grief to those of us trying to use it?:(
So much thanks to anybody who can help!