comment on

What you do is insufficient. Have you ever played with nmap? It is capable of guessing the operating system by probing the TCP implementation.

If you really want to get away with this, besides the legal problems, you will want to make a windows machine proxy everything while doing the actual calls to the apache server.

However, I must agree with the other comments about legal issues.

If your client failed to specify acceptable platform software, you might get the money by legal moves and then your client will have to pay for a second copy that complies to their new, accurate specification.

In general, I consider proper specification and acceptance criteria vital to any code-for-hire development, and most development in general.

In reply to Re: Altering "Server" HTTP Header Param by Jeppe
in thread Altering "Server" HTTP Header Param by gryphon

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks