Post Reply 
Content of killed.html shown as text
Nov. 26, 2011, 05:23 PM
Post: #1
Content of killed.html shown as text
Hello,

I noted that the html codes in killed.html is shown as text rather than like a web page.

Using the header filter:
URL-Killer: kill-a-URL (out)

Replacement:
URL killed \k

Proxomitron ver 4.5
Browser: Firefox 7

Is this a browser issue or ... ?
Add Thank You Quote this message in a reply
Nov. 26, 2011, 06:15 PM
Post: #2
RE: Content of killed.html shown as text
(Nov. 26, 2011 05:23 PM)femp1345 Wrote:  Is this a browser issue

I don't think so.
Open the Proxomitron's log window, enable "Local file requests",
what is the Content-Type header for "killed.html"?
Add Thank You Quote this message in a reply
Nov. 26, 2011, 09:35 PM
Post: #3
RE: Content of killed.html shown as text
From the log, I think the ad is killed by the filter "URL-Killer"
And the replaced local file is treated as text/plain by Proxomitron (Content-Type)
Add Thank You Quote this message in a reply
Nov. 26, 2011, 11:50 PM
Post: #4
RE: Content of killed.html shown as text
Interesting, for what address is the Proxomitron returning a local file that is Content-type: text/plain?

I set the URL-Killer to block everything.

The Log looks like:

Code:
+++GET 3+++
GET / HTTP/1.1
Host: www.google.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
URL-Killer: URL killed

+++RESP 3+++
HTTP/1.1 200 Local file
Date: Sat, 26 Nov 2011 23:07:09 GMT
Server: Proxomitron
Connection: close
Last-Modified: Wed, 21 Apr 1999 08:01:00 GMT
Content-Length: 68
Content-type: text/html
+++CLOSE 3+++

I can see that the Proxomitron caught the request and returned a local file, Content-type: text/html.
Browser displays empty page, source code is

Code:
<!--//--><html><head><title>Connection Killed!</title></head></html>

When I requested something that might be an image

Code:
+++GET 6+++
GET /image.jpg HTTP/1.1
Host: www.google.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
URL-Killer: URL killed

+++RESP 6+++
HTTP/1.1 200 Local file
Date: Sat, 26 Nov 2011 23:19:12 GMT
Server: Proxomitron
Connection: close
Last-Modified: Fri, 08 Jan 1999 10:47:22 GMT
Content-Length: 55
Content-type: image/gif
+++CLOSE 6+++

the proxomitron returned a local file, Content-type: image/gif aka killed.gif.
Add Thank You Quote this message in a reply
Nov. 27, 2011, 04:12 PM
Post: #5
RE: Content of killed.html shown as text
I'll guess, the blocked address does not appear to be an image and that the Proxomitron returns "killed.html", Content-type: text/html.
However, the browser is expecting a file for a dynamic element or an image and displays the contents of "killed.html".

If so, you may need to provide a more appropriate file, no file, or filter some code in the page's html.

HTH
Add Thank You Quote this message in a reply
Nov. 27, 2011, 09:38 PM
Post: #6
RE: Content of killed.html shown as text
Thank you for the reply.

It was noted in a few ads. One of it being over a flash player.

I modified the killed.html to a single character which eliminated most of the problems..., except in some banner-like ads which are filled with a completely opaque background.
Add Thank You Quote this message in a reply
Post Reply 


Forum Jump: