Jump to content

Beamer

Members
  • Posts

    6
  • Joined

  • Last visited

Beamer's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Folks - all that \par and {} business indicates the original file was saved as an RTF and not plain text. Whatever editor you are using you should turn off Rich Text and/or save as plain text (if the editor has a save as HTML that should also work).RTF is great for some things - terrible for others.
  2. This is a very interesting thread - a lot more calm than the old days when I used to browse usenet.I'm probably a little too old for the group but my first browser was Mosaic. It worked but we didn't know what this "www" thing was. When Netscape showed up it was world wide web heaven. But somewhere along the way Netscape really took a dive - and while it is fashionable to blame IE for that, it wasn't just marketshare. Netscape got bad - buggy and hard to use. Once IE won the war, the internet stock bubble crashed and some saner heads prevailed Netscape still went all screwy on me and tried to build an entire OS into a browser.I get the standards issue - but since when has MS played nice with others? I was forced to install and test with FireFox late last year because we have customers using FireFox and we have some web-based features in our products. We had to make some changes (we've been supporting IE and Netscape for years) to support FireFox correctly but we did it. When IE7 hits the mainstream and the next versions of Netscape and FireFox come out we'll probably have to make more changes. That's the nature of our business and as the world continues to move forward this is getting harder, not easier to keep up with.But more specifically again with the browsers - while I appreciated tabbed browsing in FireFox I had to switch back to IE. Too many pages that I visit did not work with FireFox. I had so many error messages pop up and pages fail with FF that I couldn't stand it. So the answer, you say, is FF is extendable and can be made to work with anything. True - but I have absolutely no control over my PC at work. It is locked down. I can't add things to it, I can't install things, I can't configure things. This is typical of a corporate work environment. IE works for *me* out of the box, FF does not. Winner - IE. I don't need to see my email, the weather, listen to music. I need the web pages to view correctly, I've got Outlook, Media Player and a window in the hall for those other items I agree you aren't going to move MS by complaining about IE. What will move MS on IE is for all the major players to start prefering FF or something else. Any ideas on the chances of that happening? I'm done rambling - thanks for the board - it's A Good Thing
  3. Okay - to put this one to bed - I spoke with a learned web server person. As usual the problem is with me and not the server.Perl was sending the HTTP header as "<content-type: text/html>" which is wrong (I wonder where I got that from? I always steal stuff so I doubt I made it up). Changing the line to "Content-type: text/html" makes all the browsers happy.So my guess is IE doesn't care or was able to make sense out of the mangled header and the Mozilla browsers were demanding I do it right.Thanks for your help.
  4. Thanks aspnetguy. Problem #2 in your referenced link is exactly my problem. I see that 'Content-type "application/octet-stream"' message in one of the browsers I tried.So it is off to find the server guy and explain the problem.Now if some IE guru could tell me what IE is doing to ignore that I'd really like to know (I test software for a living and knowing this sort of thing would be nice - thankfully I don't test web applications or I'd probably have gone loony ages ago )
  5. This is all happening on an intranet that is inaccessible outside the firewall. It is a Windows based server. I have no control over the server nor would I know what to do with it if I did But I could probably ask someone if I know what, specifically, to ask. I guess the big question here is why IE is doing the right thing and Netscape/Firefox is not (and yes I know IE is probably not "doing the right thing" specifically but it is doing what I want it to do).The redirect code is very simple:<html><head><meta http-equiv="Refresh" content="1;url=http://SOMEINTERNALSERVER/cgi-bin/qasds.pl" /></head><body><p> You will <a href="http://SOMEINTERNALSERVER/cgi-bin/qasds.pl">redirected</a> in one second. If you seethis message after one second, please click on the redirected link. </p></body></html>
  6. I'm trying to do something simple but I'm not being very succesfull. Brief description: I have a text file which defines a list of executables which need to be available for download by people on my team. I have written a Perl script which reads this file and spits out an HTML page. The text file is good, the Perl script is working great.What I'd like to do is have this be dynamic. Why build the web page after each edit of the text file when I can just call the Perl script directly? In order to make life even easier for the end users I figured a redirect would be best. So they go to the page they always go to and I have that page redirect them to my Perl script (which is sitting in the cgi-bin directory of a local web server).This works like a charm when I'm using IE (I tried Windows 6.0, 5.5 and Mac 5.2) and it works fine when I'm using Safari (I tried 1.3 and 1.0.? I think). But this fails miserably on every Netscape and Firefox browser I tried (Netscape 4.77, 6.1, 7.2 Windows and Mac and Firefox 1.0.3 and 1.5, Windows and Mac).The mozilla stuff just asks me what to do with the Perl file (save or open). In fact this really doesn't involve redirect, it does the same thing if I access it directly. Any thoughts on how to make this work correctly?Thanks
×
×
  • Create New...