Re: Changes/Bugs in Apache? -- WEB400

If you belong to Common, there is a presentation that I have done that has
all the many differences between the 2 versions of apache all laid out.
Also, yes, the security model COMPLETELY changed. But, we were a bit
nicer, we have include the OLD security module in the new Apache 2.4
release so that a server will start up on the new IBM i release and will
continue to be secure. If you need to make any changes, you do need to
convert over to the new security model. Also, the 7.2 Memo to Users has a
pretty detailed section on these changes.

Tim

Tim Rowe, timmr@xxxxxxxxxx
Business Architect Application Development & Systems Management for IBM i
IBM i Development Lab, Rochester, MN
(507) 253-6191 (Tie) 553-6191

http://www-03.ibm.com/systems/power/software/i/are/index.html

----- Original message -----
From: Jeff Stojevich <jeff.stojevich@xxxxxxxxxxxxxx>
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
Cc:
Subject: Re: [WEB400] Changes/Bugs in Apache?
Date: Tue, May 16, 2017 1:04 PM

We are currently on V7R1 (apache 2.2) and looking at going to R2 or R3
later this year and that is on our check list to see what directives
changed in apache 2.4.

I believe they also removed the allow/deny directives for doing
authentication and authorization.

Back on June 9, 2014 Dan Burger wrote a small article on this on "The
Four Hundred" web site

-----Original Message-----
From: WEB400 [[1]mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Jon
Paris
Sent: Tuesday, May 16, 2017 9:29 AM
To: Web400@Midrange. Web400 <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Changes/Bugs in Apache?

That is quite possible Jeff - we went direct from V7R1 to V7R3 and this
is the first time I have tried to use these test services since then.
I have it working by using a simplified directive and having a separate
AliasMatch for each web service. For now I'll live with that until I
have more time to get a more generic process working.

For the record I am now simply using ScriptAlias /restsrv1
/qsys.lib/partner400.lib/restsrv1.pgm and ScriptAlias /restsrv2
/qsys.lib/partner400.lib/restsrv2.pgm etc. Luckily I only have three to
test right now!

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

> On May 16, 2017, at 9:40 AM, Jeff Stojevich
<jeff.stojevich@xxxxxxxxxxxxxx> wrote:
>
> Is this one of the apache directives that changed when going from V7R1
to V7R2 or V7R3. There are come directives that worked in V7R1 but they
changed and IBM said they will not be backward compatible.
>
>
>
>
> -----Original Message-----
> From: WEB400 [[2]mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Jon
> Paris
> Sent: Saturday, May 13, 2017 6:30 PM
> To: Web400@Midrange. Com <web400@xxxxxxxxxxxx>
> Subject: [WEB400] Changes/Bugs in Apache?
>
> I have this directive in my Apache config (actually in the vhosts but
> ...)
>
> ScriptAliasMatch ^/CGI/(.*) /QSYS.LIB/PARTNER400.LIB/$1.PGM
>
> I have not changed it (honestly) and I am sure that it has been
working for years. This might be the first time I have used it since
moving to V7R3.
>
> When I try to use it with a REST web service (i.e. additional data in
the URL) I am getting very strange results.
>
> This URL
[3]http://partner400.com/cgi/prodrpt2oa <[4]http://partner400.com/cgi/prodrpt2oa>
works just fine and runs the script correctly.
>
> This one [5]http://partner400.com/cgi/restsrv1/part1
> <[6]http://partner400.com/cgi/restsrv1/part1> gives
>
> Not Found
> The script request is not valid. The script is not executable.
>
> The log indicates that no PGM object was identified. So just for
> chuckles I added .pgm to the base URL i.e:
> [7]http://partner400.com/cgi/restsrv1.pgm/part1
> <[8]http://partner400.com/cgi/restsrv1.pgm/part1>
>
> That works - kind of ... the correct routing takes place and the
script is called BUT the ".pgm" text then gets _added_ to the end of the
URL. i.e. "part1" is actually passed to the script as "part1.pgm". If I
add a / following "part1" then ".pgm" is seen as the next element in the
path.
>
> I've searched for PTFs on the topic but am seeing nothing.
>
> Anyone got any ideas? This is an Apache feature that we use a lot and
the .pgm workaround will not work for some scripts. For example this URL
[9]http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5 <[10]http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5>
tags the ".pgm" onto the end of quantityquery
<[11]http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5>
even when the trailing / is present as shown.
>
>
> Jon Paris
>
> www.partner400.com
> www.SystemiDeveloper.com
>
> --
> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
> mailing list To post a message email: WEB400@xxxxxxxxxxxx To
> subscribe, unsubscribe, or change list options,
> visit: [12]http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
[13]http://archive.midrange.com/web400.
>
>
> --
> This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
> mailing list To post a message email: WEB400@xxxxxxxxxxxx To
> subscribe, unsubscribe, or change list options,
> visit: [14]http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> [15]http://archive.midrange.com/web400.
>

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

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

References

Visible links
1. mailto:web400-bounces@xxxxxxxxxxxx
2. mailto:web400-bounces@xxxxxxxxxxxx
3. http://partner400.com/cgi/prodrpt2oa
4. http://partner400.com/cgi/prodrpt2oa
5. http://partner400.com/cgi/restsrv1/part1
6. http://partner400.com/cgi/restsrv1/part1
7. http://partner400.com/cgi/restsrv1.pgm/part1
8. http://partner400.com/cgi/restsrv1.pgm/part1
9. http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5
10. http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5
11. http://partner400.com/cgi/restsrv2.pgm/quantityquery/?partnum=0000011&quantity=5
12. http://lists.midrange.com/mailman/listinfo/web400
13. http://archive.midrange.com/web400
14. http://lists.midrange.com/mailman/listinfo/web400
15. http://archive.midrange.com/web400
16. http://lists.midrange.com/mailman/listinfo/web400
17. http://archive.midrange.com/web400
18. http://lists.midrange.com/mailman/listinfo/web400
19. http://archive.midrange.com/web400