Icon View Thread

The following is the text of the current message along with any replies.
Messages 21 to 24 of 24 total
Thread Trying to deploy app
Wed, May 17 2017 4:46 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< Correct for the root - but if you use a subfolder, you need a trailing slash. >>

Okay, but what is that URL pointing to ?  The root of the domain is the root of the content folder.  Other than with the case of a default document specification, which doesn't apply when you aren't using the root folder, what exactly do you expect the EWB Web Server to serve up with such a URL ?

Tim Young
Elevate Software
www.elevatesoft.com
Wed, May 17 2017 6:41 PMPermanent Link

Uli Becker

Tim,

> Okay, but what is that URL pointing to ?  The root of the domain is the root of the content folder.  Other than with the case of a default document specification, which doesn't apply when you aren't using the root folder, what exactly do you expect the EWB Web Server to serve up with such a URL ?

Running different apps on the same domain is what I mean:

http://www.mydomain.com

http://www.mydomain.com/app1/index.html
http://www.mydomain.com/app2/index.html

etc.

Since the default document is index.html I'd expect

http://www.mydomain.com/app1
or
http://www.mydomain.com/app2

to work without trailing slash.

But you are right - my initial post was wrong: the root doesn't need a
trailing slash.

Uli
Thu, May 18 2017 7:46 AMPermanent Link

Matthew Jones

Uli Becker wrote:

> Since the default document is index.html I'd expect
>
> http://www.mydomain.com/app1

I don't think this should do what you expect, but you are right to expect it! My initial feeling was that sub-directories should be left "secure". But as with IIS, the purpose of the default document is to seek the document if no file is provided, irrespective of the path. And the EWB server documentation implies this too. And of course it makes sense when you think of it like that. As some stack overflow answer points out, the default document is not the same as a starter page. And starter page is how I always felt it was, but it shouldn't be.

Perhaps the easy solution is an additional option, to specify if the default should apply in sub-directories too.


--

Matthew Jones
Thu, May 18 2017 11:57 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Uli,

<< Running different apps on the same domain is what I mean:

http://www.mydomain.com

http://www.mydomain.com/app1/index.html
http://www.mydomain.com/app2/index.html

etc.

Since the default document is index.html I'd expect

http://www.mydomain.com/app1
or
http://www.mydomain.com/app2

to work without trailing slash. >>

Ahh, yes, that isn't the way that the default document works.  It is *only* for use with the root content folder when no specific resource is requested.

What you're looking for will be coming with the EWB Web Server runtime additions.  As part of the new runtime, you will be able to hook into various parts of the request servicing process, including routing/URL rewriting.

Tim Young
Elevate Software
www.elevatesoft.com
Previous PagePage 3 of 3
Jump to Page:  1 2 3
Image