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



Hi Alfredo,

thanks for the clarification.

It appears that it's not sending the "last chunk" indicator in the chunked transfer coding. (That's the final 0 you see in your "right" example, but don't see in your "wrong" example.)

I have no clue why that would be the case. I can't imagine that would be a configuration issue -- it's a part of the transfer coding. It wouldn't be an optional feature you could set up wrong.

Try your TELNET example again, this time specify HTTP/1.0 instead of HTTP/1.1 -- version 1.0 of HTTP didn't support the chunked transfer coding, so theoretically, it shouldn't exhibit the problem.

I would assume that it's a bug in the program code. Possibly it's buffering the output, and never flushing the final buffer.

If you look at the config file you posted for port 4443, you'll see this:

BrowserMatch ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0


This code is working around a bug in Internet Explorer by downgrading the connection to HTTP/1.0. It's there for a separate problem -- but I have a feeling it'd solve your problem as well. You might (as a test, if nothing else) try inserting this into the 8000 config file -- though, make it broader so that it matches all browsers -- and see if that helps..?

It'd just be a workaround, of course. It would have a negative impact on performance -- but who knows, you may never even notice the difference.


Alfredo Delgado wrote:
Scott, if you connect on port 8000 the page will "show up" because most of
the content is coming from another server. However, you should see that the
GET on index.php doesn't close and your browser should keep trying to finish
loading the page.

Here's what it looks like from telnet...

Right:
$ telnet www.pinnacle-plastics.com 80
Trying 65.79.168.7...
Connected to www.pinnacle-plastics.com.
Escape character is '^]'.
GET /index.php HTTP/1.1
host: www.pinnacle-plastics.com

HTTP/1.1 200 OK
Date: Thu, 29 Jan 2009 18:33:02 GMT
Server: Apache
X-Powered-By: PHP/4.3.11
...removed for brevity...
</html>
<!-- 1233254002 -->
0

Wrong:
$ telnet pinnacle-plastics.com 8000
Trying 65.79.168.7...
Connected to pinnacle-plastics.com.
Escape character is '^]'.
GET /index.php HTTP/1.1
host: www.pinnacle-plastics.com

HTTP/1.1 200 OK
Date: Thu, 29 Jan 2009 18:37:46 GMT
Server: Apache/2.2.6 (Unix) mod_ssl/2.2.6 0x Zend Core/2.6.1 PHP/5.2.6
X-Powered-By: Zend Core/2.6.1 PHP/5.2.6
...removed for brevity...
</html>
<!-- 1233254280 -->


On Thu, Jan 29, 2009 at 13:06, Scott Klement <web400@xxxxxxxxxxxxxxxx>wrote:

Alfredo,

I'm having a hard time following you. I tried connecting to both of the
links you provided (port 8000 and port 4443) and both load up without
any problems in my browser.

What do you mean that it "hangs"?



Alfredo Delgado wrote:
I've been working on moving off our "roll your own" PHP install to Zend
Core/Platform. Since we don't utilize any of the IBM i features of the
native Apache I've been trying to deploy directly to the copy of Apache
that
Zend installs in PASE.

Part of successfully running directly in PASE would involve making SSL
connections. At this point I can make SSL connections but straight HTTP
connections hang and won't close when SSL is enabled. I've got a ticket
in
with Zend but I'm wondering if I'm missing something simple in the conf
files or if I'm just a glutten for punishment for wanting to avoid having
to
proxy from one Apache to another.

Most of the content is being served through a native instance running on
port 80 but you can see what I'm talking about via these ports:

http.conf: http://code.midrange.com/f55e7c0fc9.html
http://www.pinnacle-plastics.com:8000/

ssl.conf: http://code.midrange.com/ebc85621e8.html
https://www.pinnacle-plastics.com:4443/

Thanks,
Alfred

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.