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



Alfred,

So, how do you configure this? I have always been a little uncertain exactly *where* the "true" PHP server resides. Is it at 8000 or at 89?

An example of how you accomplished what you described below would be helpful.

Pete


Alfredo Delgado wrote:
Todd,

If that's the choice then why not just avoid the proxy step and serve
directly off the Apache instance in PASE? That's what I'm presently doing.
The only problem I've run into so far is that if I want to make both regular
HTTP connections and SSL connection I still have to proxy through i5/OS
Apache or run two instances of Apache in PASE.

Regards,
Alfred

On Mon, Mar 16, 2009 at 17:10, <TAllen@xxxxxxxxxxxx> wrote:

As far as I can see, it is definitely the ProxyPass causing the pain. I
don't see any way around it. It looks like we'll be forced to chuck it and
move to a Windows server. I'd really rather not do that but don't have a
choice at this point. Maybe I can come back to it later if someone at Zend
can provide a way around it.

Thanks,
Todd





Pete Helgren
<Pete@xxxxxxxxxx>
Sent by: To
web400-bounces@mi Web Enabling the AS400 / iSeries
drange.com <web400@xxxxxxxxxxxx>
cc

2009-03-16 16:49 Subject
Re: [WEB400] WordPress with Zend
PHP
Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>






Jim,

When I get it going I will. Right now the proxy pass directive (I
think) is causing WordPress quite a bit of pain.

I am going to post to the WP support site but I am still not sure if it
is WP issue or one with the Apache configuration in Zend.

Should I post in the Zend i5/OS forum as well?

Pete

Jim Dillard wrote:
Pete,

Thank you for this!

Please post similar information for Wordpress. I would like to create a
link from the Zend forums to your post here regarding Wordpress.

IBM's Michael Sandberg has a post with the install instructions to many
open source applications (SugarCRM, MediaWiki, phpBB, etc.) and your
information will be another link.

Thanking you in advance!

Jim Dillard
IBM Alliance Manager
Zend

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Pete Helgren
Sent: Monday, March 16, 2009 10:51 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] WordPress with Zend PHP

Todd,

I am not using Wordpress (yet) but in Serendipty (another blog php app)
I used the default 80 port. The proxy pass directive handles the
"translation" to/from the default port you specify in the web
configuration file in Web Admin.

My (relevant) configuration settings in Web Admin look like this:
# Configuration originally created by Create HTTP Server wizard on Mon
Feb 05 16:09:18 MST 2007
.....
Listen 10.0.10.206:80 http
DocumentRoot /www/zendcore/htdocs
.....
DirectoryIndex index.html index.php
ProxyPass / http://127.0.0.1:8000/mywebroot/
ProxyPassReverse / http://127.0.0.1:8000/mywebroot/
<Directory />
Order Deny,allow
Deny From all
</Directory>

<Directory /www/zendcore/htdocs/mywebroot>
Order Allow,Deny
Allow From all
</Directory>

<Directory /www/zendcore/htdocs/mywebroot/myblogroot>
Order Allow,Deny
Allow From all
</Directory>

I do plan to install Wordpress because I have run into a couple issues
with Serendipty and would like to use Wordpress.

Pete


TAllen@xxxxxxxxxxxx wrote:

Has anyone gotten WordPress to work with the Zend PHP product? I'm

having

no success, mainly due to the fact that there are basically 2 servers

- the

native Apache server and the Zend Apache server running in PASE.

WordPress

originally set the site URL (WordPress address) as 127.0.0.1:8000

(PASE

server). Changing that to the real IP address seemed to fix the

problems

but there is another address in the settings for the blog address,

which is

set to 127.0.0.1:8000. Changing the blog address to the real IP

address

caused the WordPress home page to become unreachable.

To change the theme I had to update the blog address to the real IP

address

and then change the address back to 127.0.0.1:8000 to get to the WP

home

page.

Perhaps WordPress is too smart for its own good but it seems this

problem

could come up with other PHP applications.

Thanks,
Todd


This communication and any transmitted documents are intended to be
confidential. If there is a problem with this transmission, please contact
the sender. If the reader of this message is not the intended recipient, or
the employee or agent responsible to deliver it to the intended recipient,
you are hereby notified that any dissemination, distribution or copying of
this communication is strictly prohibited.

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