setting the proxy
Reported by Miles Poindexter | August 11th, 2008 @ 01:29 PM | in REL 0.9.21
Could the act of setting the proxy be treated more like just setting a variable? This would make the behavior easier to understand for beginners.
for example: tried: proxy '/appfiles', :url => 'http://localhost:8080' in sc-config.rb
and
new Ajax.Request('/appfiles/applications/apps/json', {
in a Controller object
and got:
PROXY: 404 /appfiles/applications/apps/json -> http://localhost:8080/appfiles/a... Date: Mon, 11 Aug 2008 19:55:08 GMT
I had been expecting it to create: http://localhost:8080/applicatio..., but instead it created http://localhost:8080/appfiles/a...
in other words, I expected the /appfiles "proxy" to get replaced by http://localhost:8080
thanks again to onitunes for helping me with the correct syntax, which was:
proxy '/appfiles', :to => 'localhost:8080', :cookie_domain => 'localhost', :url => ''
which is very confusing syntax. no?
Comments and changes to this ticket
-

Erich Ocean (onitunes) September 30th, 2008 @ 04:19 AM
- → Milestone changed from to REL 0.9.21
- → State changed from new to open
- → Assigned user changed from Charles Jolley to Erich Ocean (onitunes)
-

Erich Ocean (onitunes) November 8th, 2008 @ 09:25 AM
- → Assigned user cleared.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
SproutCore: JavaScript Application Framework
Source available from github
The Git repository resides at http://github.com/sproutit
Check out the current development trunk with:
git clone git://github.com/sproutit/sproutcore.git
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Submitting Patches
Resist adding new tags, use the ones in the tag cloud already. If you are submitting a patch or a pull request from a fork, tag the ticket as a "patch". If you are submitting a new feature enhancement, tag it as "enhancement". If you are submitting a fix for a bug, tag it as "fix".
Thanks!
We're glad you're contributing. Feel free to drop by the Google Group as well to let us know you are involved.
