default entry & Base URL := URL redirect

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

default entry & Base URL := URL redirect

Brad Fuller
In past versions, one method to redirect so the application path is not
in the URL was to change 'default entry' to your app and also to change
your apps base-path to '/'

Now, Base-path does not exist. What is the method to make your URL:

http://mydomain.com/seaside/myapp

to

http://mydomain.com/

thanks,

brad


Nevin mentioned in the past that he subclassed WAKom and implemented
#process:

process: aRequest
     aRequest url = '/'
         ifTrue: [aRequest url: '/seaside/home'].
     ^ super process: aRequest


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Lukas Renggli
> Now, Base-path does not exist. What is the method to make your URL:
>
> http://mydomain.com/seaside/myapp
>
> to
>
> http://mydomain.com/

Have a look at the thread "[Seaside] Seaside 2.7" it discusses this
towards the end. Search for #serverPath:

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Brad Fuller
Lukas Renggli wrote:

>> Now, Base-path does not exist. What is the method to make your URL:
>>
>> http://mydomain.com/seaside/myapp
>>
>> to
>>
>> http://mydomain.com/
>
> Have a look at the thread "[Seaside] Seaside 2.7" it discusses this
> towards the end. Search for #serverPath:

I assume you mean this:

"The basePath is now a setting in the application called #serverPath,
similar to #serverPort and #serverHost. To change the path you have to
change the application configuration. "

I don't quite understand it. But, I'll try and figure it out tomorrow
morning (I'm in PST)

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Florian Minjat
This one too from the same thread should interrest you :

">> I need my application to be accessible with an url

>> like 'http://myaddress/myApp' and not like
>> 'http://myaddress/seaside/myApp'. Previously I was just doing :
>> WADispatcher default basePath: ''.
>> [...]
>
> Lukas Renggli wrote:
>Aha, now I understand the problem. Evaluate the following code:
>     WADispatcher default setName: ''
>and everything should work. Thanks to the new implementation of the
>dispatchers ;-) "

Florian

Brad Fuller wrote:

> Lukas Renggli wrote:
>>> Now, Base-path does not exist. What is the method to make your URL:
>>>
>>> http://mydomain.com/seaside/myapp
>>>
>>> to
>>>
>>> http://mydomain.com/
>>
>> Have a look at the thread "[Seaside] Seaside 2.7" it discusses this
>> towards the end. Search for #serverPath:
>
> I assume you mean this:
>
> "The basePath is now a setting in the application called #serverPath,
> similar to #serverPort and #serverHost. To change the path you have to
> change the application configuration. "
>
> I don't quite understand it. But, I'll try and figure it out tomorrow
> morning (I'm in PST)
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Brad Fuller
Florian Minjat wrote:

> This one too from the same thread should interrest you :
>
> ">> I need my application to be accessible with an url
>>> like 'http://myaddress/myApp' and not like
>>> 'http://myaddress/seaside/myApp'. Previously I was just doing :
>>> WADispatcher default basePath: ''.
>>> [...]
>>
>> Lukas Renggli wrote:
>> Aha, now I understand the problem. Evaluate the following code:
>>     WADispatcher default setName: ''
>> and everything should work. Thanks to the new implementation of the
>> dispatchers ;-) "

Yeah, I saw that Florian, Thanks.

Ok, so I executed
  * WADispatcher default setName: ''
  * re-inited Seaside and Pier.
  * stopped and started WAKom (that always seems to be needed)

Now, I can go to

   http://mydomain.com:9999/seaside

and the web browser displays the application that is the Default Entry
of seaside/config.

In the particular Seaside Application config
  * place '/' in "Server Path"

With rewrite rules, it seems to work fine.

thanks!
brad

>
> Brad Fuller wrote:
>> Lukas Renggli wrote:
>>>> Now, Base-path does not exist. What is the method to make your URL:
>>>>
>>>> http://mydomain.com/seaside/myapp
>>>>
>>>> to
>>>>
>>>> http://mydomain.com/
>>>
>>> Have a look at the thread "[Seaside] Seaside 2.7" it discusses this
>>> towards the end. Search for #serverPath:
>>
>> I assume you mean this:
>>
>> "The basePath is now a setting in the application called #serverPath,
>> similar to #serverPort and #serverHost. To change the path you have to
>> change the application configuration. "
>>
>> I don't quite understand it. But, I'll try and figure it out tomorrow
>> morning (I'm in PST)
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Brad Fuller
Brad Fuller wrote:

> Florian Minjat wrote:
>> This one too from the same thread should interrest you :
>>
>> ">> I need my application to be accessible with an url
>>>> like 'http://myaddress/myApp' and not like
>>>> 'http://myaddress/seaside/myApp'. Previously I was just doing :
>>>> WADispatcher default basePath: ''.
>>>> [...]
>>>
>>> Lukas Renggli wrote:
>>> Aha, now I understand the problem. Evaluate the following code:
>>>     WADispatcher default setName: ''
>>> and everything should work. Thanks to the new implementation of the
>>> dispatchers ;-) "
>
> Yeah, I saw that Florian, Thanks.
>
> Ok, so I executed
>  * WADispatcher default setName: ''
>  * re-inited Seaside and Pier.
>  * stopped and started WAKom (that always seems to be needed)
>
> Now, I can go to
>
>   http://mydomain.com:9999/seaside
>
> and the web browser displays the application that is the Default Entry
> of seaside/config.
>
> In the particular Seaside Application config
>  * place '/' in "Server Path"
>
> With rewrite rules, it seems to work fine.

On another site, I have a question: I'm working on the squeakfoundation
site and want to know how we can do this w/o apache rewrite rules.
Specifically, it is now:

<VirtualHost *>
         ServerName www.squeakfoundation.org
         ServerAlias squeakfoundation.org
         ProxyPass / http://127.0.0.1:7780/
         ProxyPassReverse / http://127.0.0.1:7780/
</VirtualHost>

Anyone help with ideas so we can access pier at the base url?

brad


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: default entry & Base URL := URL redirect

Brad Fuller
Brad Fuller wrote:

>
> On another site, I have a question: I'm working on the squeakfoundation
> site and want to know how we can do this w/o apache rewrite rules.
> Specifically, it is now:
>
> <VirtualHost *>
>         ServerName www.squeakfoundation.org
>         ServerAlias squeakfoundation.org
>         ProxyPass / http://127.0.0.1:7780/
>         ProxyPassReverse / http://127.0.0.1:7780/
> </VirtualHost>
>
> Anyone help with ideas so we can access pier at the base url?

Just to post progress for others (most of you know this, but for those
who don't);

I tried this out on yet another site. I removed the rewrite rules and
substituted:

<VirtualHost *:80>
          ServerName my.domain.com
          ProxyPreserveHost On
          ProxyPass / http://localhost:8080/seaside/pier
          ProxyPassReverse / http://127.0.0.1:8080/seaside/pier
</VirtualHost>

The added "ProxyPreserveHost On" works just great. As long as Server
Path of pier config is set at '/'

The problem now is that I can't access my css files. onward....
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside