This was my first real attempt with an NPH script, so please be gentile.

Purely as a matter of terminology, this doesn't appear to be an NPH script. If it is, then you are failing to manually set the Status header. For that matter, even if it is a simple CGI, I don't see where the content-type header is being printed... so, I'm a little curious how it is managing to work at all.

That aside, if your coworkers are used to using dig, why would you try to shift them away from the command line to a browser? I understand your reasoning that no one in your department uses the command line "with much efficiency" but I question your decision to go to a web-based tool. The latter seems to limit even the possibility of efficiency.

For example, I imagine that at least one of your coworkers, even if not very efficient in general, is at least familiar with how to redirect output from dig into a file. With the web-based tool, he'll be reduced to cutting and pasting (or learning a command-line based browser, maybe.)

Creating a more flexible and powerful tool is a great idea, but tacking a web interface onto things doesn't often accomplish that. The command line is your friend!

-sauoq
"My two cents aren't worth a dime.";

In reply to Re: über dig tool (why the web?) by sauoq
in thread über dig tool by vbrtrmn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.