I don't have a blog. When I have something to write, it pretty much ends up on Perlmonks. This is (as the title suggests) more story than meditation. Maybe what I've uncovered is obvious, maybe not. I just hope it will help someone out.

I'm developing for the Solaris (Sparc) OS. Mostly things are the same, but sometimes they aren't. When I was having problems getting https://localhost/ to work, I tried using openssl to get in: 

openssl s_client -connect localhost:443

[download]
No dice -- got an error right away. Eventually, I discovered that 
openssl s_client -connect 10.1.1.161:443

[download]
worked instead. I'm sure someone can explain that -- I can't.

Next, I was trying to run a test script to hit the local webserver. Since I'd already discovered localhost wouldn't do that, I was using the IP address, which worked fine until there was a re-direct, at which point things just died quietly (i.e., nothing obvious in the web logs).

So then I tried using a browser (with the IP address, not the name) to check that things worked, and discovered that Firefox complained that the SSL certificate I had installed on this (virtual) box didn't match the IP address I was trying to use. So I put the name of the host into my test script, and was finally able to log in.

So my test script is fairly simple: try to log in as a variety of different users, each with a different set of privileges, and confirm that the user can see the links that they're allowed to see, and if the link does exist, try to follow it, making sure that a valid page (HTTP code is 200) gets returned.

Since some of the links belong to packages that aren't installed yet, I expect some of them to fail, so that part of the code is inside a SKIP block. This worked fine when I ran the script from my Ubuntu box, hitting the Solaris box, but now I'm running from within Solaris, as soon as a non-existent page is requested, the test script dies, and I'm not sure why.

The links are in a table, so I've just commented those elements out, and now my test script is passing OK -- I guess I need to go back to the docs and read them again.

Sometimes development is maddening like that.

Update: I've started a SoPW question to follow up on my last point.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Stories from the front by talexb

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.