Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Our users can not see images in our website, www.courtauction.go.kr with the latest firefox. We don't have any problem with firefox 3,4,5...

  • 3 replies
  • 6 have this problem
  • 5 views
  • Last reply by shji

more options

Our users can not see images in our website, www.courtauction.go.kr with the latest firefox. We don't have any problem in firefox 3,4,5 and IE, safari, chrome...

try this : http://www.courtauction.go.kr/DownFront?spec=default&dir=kj/2009/0717&filename=T_B000210200901300223049.jpg&downloadfilename=T_B000210200901300223049.jpg

Our users can not see images in our website, www.courtauction.go.kr with the latest firefox. We don't have any problem in firefox 3,4,5 and IE, safari, chrome... try this : http://www.courtauction.go.kr/DownFront?spec=default&dir=kj/2009/0717&filename=T_B000210200901300223049.jpg&downloadfilename=T_B000210200901300223049.jpg

Modified by shji

Chosen solution

You can get a "Corrupted Content Error" error if there errors in the HTTP response headers like multiple location redirects.

  • Bug 681140 - Corrupted Content error due to multiple Content-Disposition header field instances

Caused by the trailing ";" in the Content-Length response header?

nsHttpTransaction::ParseLine [Content-Length: 10091;]
invalid content-length!
Read this answer in context 👍 1

All Replies (3)

more options

I got the following on the screen:

Corrupted Content Error The page you are trying to view cannot be shown because an error in the data transmission was detected.

The page you are trying to view cannot be shown because an error in the data transmission was detected.

  • Please contact the website owners to inform them of this problem.
more options

Chosen Solution

You can get a "Corrupted Content Error" error if there errors in the HTTP response headers like multiple location redirects.

  • Bug 681140 - Corrupted Content error due to multiple Content-Disposition header field instances

Caused by the trailing ";" in the Content-Length response header?

nsHttpTransaction::ParseLine [Content-Length: 10091;]
invalid content-length!
more options

You saved me! I don't know how to thank you. God bless you~