Re: [EXTERNAL] Re: Silly question: HTML 5

This all appears to just be standard routing configurations. HTML5 just
lets you do some things directly that you used to have to have some sort of framework to do.

Yeah, sorry if I gave the impressions there were breaking problems or major rewrites needed. I was just saying that, depending on what you are using in HTML5, the switch to HTML5 might require some adjustments to Apache. You might need to modify the ProxyHTMLDocType directive if it's important to have the DocType be correctly defined as HTML5 (that was my first link). You might need to modify .htaccess if you are using the HTML5 pushstate API. I don't know what else you might run into as you start using other HTML5 APIs and technologies.

Thanks,

Kelly Cookson
Senior Software Engineer II
Dot Foods, Inc.
217-773-4486 ext. 12676
www.dotfoods.com<http://www.dotfoods.com/>

From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Bucknum
Sent: Friday, August 23, 2019 10:14 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WEB400] [EXTERNAL] Re: Silly question: HTML 5

This all appears to just be standard routing configurations. HTML5 just lets you do some things directly that you used to have to have some sort of framework to do. All of the examples look just like what I have to use to get my Zendframework sites to work correctly.