× 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.



It looks like that "error" occurs when you try to view the HTML source code.
My logs indicate that the HTTP header is invalid.
I had this issue previously and corrected it, but when we moved from the old 170
on V4R5 to the 520 on V5R3 I may have rolled back my source code Viewer and
reintroduced the error. It only occurs with HTML, and so you may look at what
HTTP header you are sending.
Again, remember, that the HTTP header is terminated with two consecutive
linefeeds and any "headers" you send after the two linefeeds are NOT interpreted
as headers.  
For example, this is a one-line HTTP header:

'Content-Type: text/html' + X'2525'

This is a two-line HTTP Header:
'Content-Type: text/html' + X'25'
'Status: 200 Hello World' + X'2525'

(contrived by to illustrate the linefeed issue)


-Bob Cozzi
www.RPGxTools.com
RPG xTools - Enjoy programming again.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf
Of Shane_Cessna@xxxxxxx
Sent: Friday, April 28, 2006 7:39 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] CGI error...

I tried Scott's suggestion, to no avail...

my CGIDEBUG file acts like it's not even getting to my clrhtmlbuffer(); 
line of code...

Shane Cessna  
Senior iSeries Programmer
iSeries WebSphere & Tomcat Administrator
North American Lighting, Inc.
(618) 662-4483 x2776
shane_cessna@xxxxxxx 



Robert Cozzi <cozzi@xxxxxxxxx> 
Sent by: web400-bounces@xxxxxxxxxxxx
04/27/2006 05:47 PM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] CGI error...






The GET limit is around 4k but really isn't 4k.
The POST limit is unlimited.



On 4/27/06 3:55 PM, "Matt.Haas@xxxxxxxxxxx" <Matt.Haas@xxxxxxxxxxx> wrote:

> You should use a POST for sure. URL's have length limits that vary
> somewhat but typically you start having problems around 1024 characters.
> Also, GET data is written to the log files so long URL's take up more
> disk space. POST data can be much longer. I think the default limit is
> around 10MB but that can be changed.
> 
> Matt 
> 
> -----Original Message-----
> From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
> On Behalf Of Shane_Cessna@xxxxxxx
> Sent: Thursday, April 27, 2006 4:44 PM
> To: Web Enabling the AS400 / iSeries
> Subject: Re: [WEB400] CGI error...
> 
> Is there a length limit on what you can send though get or post???
> 
> I have a textarea field on a form that's 500 characters, user field
> that's 
> 10, reqnum field that's 12, and altflag field that's 1...
> 
> Shane Cessna 
> Senior iSeries Programmer
> iSeries WebSphere & Tomcat Administrator
> North American Lighting, Inc.
> (618) 662-4483 x2776
> shane_cessna@xxxxxxx 



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.