Opened 16 years ago

Closed 16 years ago

#9934 closed (invalid)

Django is generating requests that result in untyped binary data download in FF 3

Reported by: voidfiles Owned by: nobody
Component: HTTP handling Version: 1.0
Severity: Keywords:
Cc: voidfiles@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Hi,

I am having a problem that seems like a ghost. I can find where it's

comming from. It doesn't happen all the time. But what happens is
sometimes when I go to a page. instead of loading the page, the
browsers askes me if I would like to download a file called untyped
binary data.

I am hosting the project on dreamhost. I am use fcgi.

I am starting the requests here in a dispatch.fcgi

#!/home/mysite/opt/bin/python
import sys, os

from flup.server.fcgi import WSGIServer
from django.core.handlers.wsgi import WSGIHandler

# Add a custom Python path.
sys.path.insert(0, "/home/mysite/site_code")

# Switch to the directory of your project. (Optional.)
os.chdir("/home/mysite/site_code")

# Set the DJANGO_SETTINGS_MODULE environment variable.
os.environDJANGO_SETTINGS_MODULE = "mysite.settings"

WSGIServer(WSGIHandler()).run()

This is what the file looks like that it asks me to download


Attachments (1)

WWUdGtcF.dms.part (2.6 KB ) - added by voidfiles 16 years ago.
This is the body of the file it asks me to download.

Download all attachments as: .zip

Change History (4)

by voidfiles, 16 years ago

Attachment: WWUdGtcF.dms.part added

This is the body of the file it asks me to download.

comment:1 by voidfiles, 16 years ago

I have been investigating this further, and if you look at the file I attached there is a character at the the front of the HTTP/1.1 I think that might be throwing off the browser.

comment:2 by voidfiles, 16 years ago

Cc: voidfiles@… added
Component: UncategorizedHTTP handling

comment:3 by Jacob, 16 years ago

Resolution: invalid
Status: newclosed

I can't reproduce this, nor have I ever seen this behavior before on any Django install. I have to assume it's a misconfigured web server on your end, but please feel free to reopen if you can indeed trace this back to a Django bug.

Note: See TracTickets for help on using tickets.
Back to Top