Forums

Posting in these forums is disabled. These forums will be available for archive purposes. Please join the new forums at the links below:

  • yui-support - replaces the `YUI 3.x` and `YUI 3 Gallery` forums.
    We have created the following discussion categories within this group to aid discoverability for these most-used topics:
    • Charts for YUI Charts support.
    • DataTable for YUI DataTable support.
    • Gallery for YUI Gallery support, including support for published Gallery components as well as the Gallery process in general.
    • Tools for support of YUI’s suite of developer tools such as selleck, shifter, grover, yogi, etc.
    • Everything Else for questions that don’t fit one of the categories above, we’ve got you covered here.
  • yui-deprecated - replaces the `YUI 2.x` forum and the forums of other deprecated products (`YUI Doc`, `Builder`, `YUI PHP Loader`, etc.).
  [ 2 posts ]
New Topic | Post Reply | Print view
Previous topic | Next topic

Eric Low

  • Joined: Fri Oct 12, 2012 12:20 pm
  • Posts: 1
  • Offline
  • Profile

script not found and loaded

Post Posted: Tue Nov 20, 2012 1:59 pm
In my test page, I have a reference to a script:

<script src="../../../main/resources/js/thinger.js" type="text/javascript"></script>

When I open the test page in a browser, the resource location is resolved fine:
file:///C:/Projects/dev/myproject/js/build/trunk/src/main/resources/js/thinger.js

However, when I load the same test file using Yeti, the resource location is resolved to:
http://localhost:9000/agent/13534437873 ... thinger.js

and as a result, is not found.


Your thoughts on how to proceed?

Dav Glass

  • Username: davglass
  • Joined: Thu Aug 28, 2008 9:28 am
  • Posts: 2088
  • Location: Marion, IL, US
  • Twitter: davglass
  • GitHub: davglass
  • Gists: davglass
  • IRC: davglass
  • Offline
  • Profile

Re: script not found and loaded

Post Posted: Mon Nov 26, 2012 2:48 pm
Make sure when you are starting up yeti that you are in the directory you want to serve from. So if you are fetching a resource from `../../../`, then you should run yeti from `../../../` from where you are. Yeti needs to have access to the files and only serves files relative to where it's started from (for security).
  [ 2 posts ]
New Topic | Post Reply | Print view
Previous topic | Next topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum