Bug 1520 – status.html does not always return content-type

Bug 1520 - status.html does not always return content-type

Summary:

status.html does not always return content-type

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	6.1.0
Platform:	PC All

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-05-09 08:47 UTC by Michael Herger
Modified:	2008-09-15 14:37 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
first set content-type, then return on "empty" document (718 bytes, patch) 2005-05-09 08:51 UTC, Michael Herger	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Herger 2005-05-09 08:47:28 UTC

status.html does sometimes not return a correct content-type, therefore displaying wrong characters in 
the web interface.

Comment 1 Michael Herger 2005-05-09 08:51:09 UTC

Created attachment 505 [details]
first set content-type, then return on "empty" document

For some odd reason Web::Pages::status does sometimes return an empty document
- and still display the status page :-/. Web::HTT::generateHTTPResponse will in
this case return prematurely before setting the content type. If we move it
after that check, the page displays fine.

Comment 2 Michael Herger 2005-05-10 23:45:08 UTC

Change 3155 fixes this.

Comment 3 Chris Owens 2006-06-16 14:41:16 UTC

There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.