Looks like the Content-Type of application/xhtml+xml caused the problem on IE.
Adding the line, as suggested by Jeremy:
print STDOUT "Content-type: text/html\n";
before Analog is called on line 88 appears to have fixed the problem.
BTW, I also tried adding " 2>NUL" at the end of line 88, but it did not make any difference that I could tell.
Thank you to everyone who helped out, and especially to Jeremy who took the time to analyze the HTTP headers.
Now I can go and play with all the new reporting features :)
Best Regards,
Lapo Nustrini
On Wednesday, November 5, 2003, at 09:42 AM, Jeremy Wadsack wrote:
This may only be related to deploying the Perl file on IIS because IIS echoes error messages to the browser instead of a log file. The headers that are coming through show Analog's warning ("Redirecting future diagnostic messages to...") which might be confusing the browser.
It also has the Content-type set to application/xhtml+xml which might be confusing Internet Explorer.
The first issue you can probably resolve by adding " 2>NUL" to the end of the analog command at line 88 in anlgform.pl.
The second issue, unfortunately, is built into analog.exe. You *might* be able to work around it by adding a header line before Analog outputs, something like
print STDOUT "Content-type: text/html\n";
before line 88 in anlgform.pl.
The content-type that Analog is using is the proper one, but as it was registered in early 2002 as an RFC which may have been too late to make it into IE5 (although IE6 should know it). (See http://www.w3.org/TR/xhtml-media-types/ for gory details.)
[Stephen:] Perhaps the Content-type header should be configurable? Or at least use the allows text/html for the time until more support for application/xhtml+xml is available?
--
Jeremy Wadsack Wadsack-Allen Digital Group
On Tuesday, November 4, 2003, at 05:29 PM, Jeremy Wadsack wrote:
Lapo Nustrini <[EMAIL PROTECTED]> (Tuesday, November 04, 2003 5:18 PM):
No, no. You need to inspect the HTTP headers. That's before the file
and are never shown in the browser. I suggested Firebird's extension
as one tool. You could use wget or curl or some command-line spider
with a "show headers" option tool, too.
Ok. That makes more sense. I guess I need to install something to debug this. I was hoping to avoid doing this.
If it's a publicly available URL I can check it for you.
--
Jeremy Wadsack Wadsack-Allen Digital Group
+---------------------------------------------------------------------- --
| TO UNSUBSCRIBE from this list:
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| Digest version: http://lists.isite.net/listgate/analog-help-digest/
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
+---------------------------------------------------------------------- --
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
