Re: HELP! OWAS 3.01 NT - valid virtual host error

From: Jason Archambeau <jason.archambeau_at_mci2000.com>
Date: Sun, 16 Aug 1998 15:17:12 GMT
Message-ID: <01bdc92b$a0068340$773537a6@GATOR.internetMCI.COM>

I think the problem may be:

When you set up your web Listener, you had to specifiy a host name. Verify that this is EXACTLY the same host name that you are using in the URL. Sometimes, the hostname in the Listener config file has the fully qualified DNS name attatched like so:

	If your host is named 'beta' and your DNS domain is 'mydomain.com' then
          the Listener.cfg file may have a valid host as: 

'beta.mydomain.com'. This will be the ONLY valid host for this listener (unless you define others)

If all else fails, try using the IP address in the URL instead of the hostname. If this works, then it is definitely a problem with the hostname that the Listener considers as 'official'.

Jason

jj_at_b4s.com wrote in article <35d32a21.89025251_at_nntp.best.com>...
> When a web browser on another machine tries to access my OWAS 3.01
> site on an NT 4.0 SP3 workstation, I get the following error message:
>
>
> ============================================================
> Unable to open http://<sitename>. The site reported an invalid
> request.
>
> ------------------------------------------------------------------------
> The request did not specify a valid virtual host.
>
> ============================================================
>
> The wierd thing is that when I access the site using a browser that is
> on the same machine as OWAS, everything works perfectly.
>
> There is no problem pinging my sitename on the network and I get the
> same error message whether I use the direct IP address or the actual
> sitename.
>
> Also this is not a PLSQL / cartridge type of problem because this
> problem just occurs when accessing static HTML.
>
> The OWAS is setup with the default security settings that were
> defaulted during installation of OWAS and as far as I can tell there
> is no default security setting that might be causing my problem.
>
> When this problem occurs no messages are put into the "svwww.err" file
> or the default "xlf.log" file.
>
> Any suggestions anybody?
>
> I can't find any help in the Oracle documentaion that deals with such
> an error.
>
> From memory, I thought I had seen some debugging tip where you could
> use telnet to the http deamon at port 80 and possibly do some
> debugging that way? If I did this from another machine on the network
> perhaps I could get a better idea of where the problem lies.
>
> One other thing has anybody got any success/horror stories with trying
> to use OWAS 3.01 under NT? Any opinions on the Oracle (Spyglass) web
> listener, or are people have great success with using the Microsoft,
> Netscape or Apache servers?
>
> Any help would be greatly appreciated.
>
Received on Sun Aug 16 1998 - 10:17:12 CDT