× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: NEW!!!! UPDATE - Domino Being Served by IBM HTTP
  • From: Fred Newberry <fnewberry@xxxxxxxxxx>
  • Date: Mon, 11 Dec 2000 08:53:32 -0600

It turns out that if your Domino Agents contain a Print
"Content-Type:text/html", then the agent is control of all HTML production.
That is not problem, the problem is that if the  Print
"Content-Type:text/html" does not contain a space after the colon there is a
problem.  So the PROPER way to write the statement is  Print "Content-Type:
text/html"   (note the space : text ).
Doing that allows the 2 products (IBM HTTP and Domino) to work together much
better and they seem to be ok.

Fred.


>  -----Original Message-----
> From:         Fred Newberry  
> Sent: Wednesday, December 06, 2000 2:47 PM
> To:   'Domino400 (E-mail)'; 'JAVA400-L@midrange.com'
> Subject:      RE: UPDATE - Domino Being Served by IBM HTTP
> 
> 
> It turns out that via the -vv option on starting the server instance the
> cause has been found.   It seems that the Service Programs that inable IBM
> HTTP to serve Domino appear to be the problem.   The content type and
> HTFORMAT information both come back with  ext/html in the data.  This
> seems to be coming from the ICAPI process.    
>       HTTPDAPI ICAPI:  HTTPD_set() args..... name=HTTP_Content-Type ; name
> size= 17
>       HTTPDAPI ICAPI:  HTTPD_set() args..... value=ext/html ; value size=
> 8 
> Now comes the task of getting a fix.
>        -----Original Message-----
>       From:   Fred Newberry  
>       Sent:   Wednesday, December 06, 2000 2:29 PM
>       To:     Domino400 (E-mail); 'JAVA400-L@midrange.com'
>       Subject:        Domino Being Served by IBM HTTP
> 
> 
>               IBM AS/400 OS V4R5  Domino V5.0.5   IBM HTTP    Websphere
> Version 3.021
> 
>               We normally run using the Domino Web Server to serve Domino
> Databases.  Those databases have some agents that generate reports by
> using the PRINT statement that puts out  HTML.   When Domino is asked by
> the browser to go to the agents URL, the resulting output of HTML from the
> agent displays in the web browser just fine. 
> 
>               We would like to be able to set up the IBM HTTP Server to do
> the Web Serving of the Domino databases.  We set Domino to use our HTTP
> Instance, the HTTP Instance has the directives set up for the necessary
> Domino service programs.   The HTTP Instance can serve standard Domino
> Forms as HTML just fine.  But when we request the above mentioned agent
> that outputs HTML, the browser gets a Security Warning that the file about
> to be downloaded (MIME Type  ext/html) should be saved locally or opend
> where it exists.      If you say to open it, you get a new browser window
> with the resultant HTML shown, the way it should have been shown in the
> current browser window.
> 
> 
>               Has anyone else seen this problem ???    I am having a very
> hard time getting a resolution.  It is very hard to tell if it is a Domino
> problem,  an IBM HTTP Server problem, or the Domino QNOTES Service
> Programs that are acting up.
> 
>       Fred A. Newberry
>       EFG Companies
>       1-800-527-1984
>        x8262
>       fnewberry@efgusa.com
> 
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.