topic static pages cut by SSL? in Operating System - OpenVMS

static pages cut by SSL?

Willem Grooters — Mon, 15 Jun 2009 12:14:17 GMT

VMS 7.3-2, SWS 2.1-1 with SSL enabled.

http://server:port1/path/page.html shows correct page, where https://server:port2/path/page.html does not: the page is incomplete and some nonprintable characters are translated into printable characters, causing link failures; see attachment ("View Source" output).

Output that is generated by a CGI script (that TYPEs a file to SYS$OUTPUT) is correct - no matter the size.

This is not browser dependent: It happens with both IE and Firefox.

What causes this behaviour?

Re: static pages cut by SSL?

John Gillings — Mon, 15 Jun 2009 20:32:59 GMT

Willem,

forgot the attachment?

Sounds like a bug to me. I'd recommend logging this with HP Customer Support.

Re: static pages cut by SSL?

Willem Grooters — Tue, 16 Jun 2009 05:00:34 GMT

I'm certain I added the attachement, but here it is again.

Re: static pages cut by SSL?

Bojan Nemec — Tue, 16 Jun 2009 05:53:18 GMT

Willem,

The output seems an VMS variable length or VFC sequential file.

Check if you have the EnableMMAP directive set to ON.

Bojan

Re: static pages cut by SSL?

Willem Grooters — Tue, 16 Jun 2009 09:36:53 GMT

EnableMMap is set to Off (default)
Switched to ON requires the file(s) to be converted to Stream_LF. Also, there was an error in the file (missing end-quote) that caused a problem when accessed using SSL but without, the brwoser seemed happy enough.

Re: static pages cut by SSL?

Willem Grooters — Tue, 16 Jun 2009 09:45:09 GMT

EnableMMap On

This can be used within a for the whole virtual host, or in if just that difrectory will be accessed.

It requires that all static files that are accessed using SSL are converted to STREAM_LF
(Create a FDL file, change FORMAT to STREAM_LF and use that FDL file in CONVERT. Changing attributes doesn't change the internal structure - which is required here). These files will be accessed with, or without SSL, and the standard EDIT has no problems with these files (unless the record size exceeds the process quota)