We have a web site that is using shibboleth. I need to exclude a portion from being protected.
So far the only way I can get this to work is by excluding an entire top level directory.
If I exclude using this things work properly.
Path name="rxxx_v10.0.25/" authType="shibboleth" requireSession="false"
When I look at the sites using developer tools I see rxx_v10.0.25/ExternalModules and rxx_v10.0.25/Resources being accessed. If I specify those paths only the URLs end up being protected instead of not being protected.
I have tried the exclusions in various order, alphabetically or in the order that they are accessed, but am having no luck.
Any suggestions/help is greatly appreciated.
Related
We recently moved our communities to the cloud and with that we moved all subfolders up one level.
So, previously we had:
www.mywebsite.com/abcd/otherstuff/index.htm
And now our folder structure is:
www.mywebsite.com/otherstuff/index.htm
We've stripped out the abcd from all URLS in the website itself. The problem is, there's lots of tech notes and bookmarks out there in the world that still point to the old URL and they are getting a 404 and a lot of people are not happy.
Is it possible to write a script that enables our communities to detect the presence of abcd in the URL, strip it out, parse the remainder and direct the browser to the correct address?
What language would one write this in? Would it go in the HTTACCESS file? Has anyone done anything similar before?
Thanks.
I haven't done it but you may find this information useful: http://coolestguidesontheplanet.com/redirecting-a-web-folder-directory-to-another-in-htaccess/
Why do relative paths not work in popular basic Content Management Systems which use "editable" class tagging? It's weird that every time I edit a page in the CMS all my styles and jS are killed because of my relative paths. What's going on behind the scenes? Are they making a duplicate copy of my page? Although that still doesn't seem to quite explain it, because forward relative paths such as
/css/style.css will still work,
but relative paths going backward such as
../css/style.css
will no longer work.
Even if they make a duplicate copy, they have FTP access and it seems like they should be able to trace relative paths... Instead they need an absolute or root-relative path.
Relative paths work fine in Surreal, but if your page has include files then the paths may "break" depending on where the page that's including it is located.
Regardless, you can adjust URL formatting pretty easily in Surreal:
<div class="editable" data-urls="absolute">
...
</div>
More details are in the docs: http://www.surrealcms.dev/docs/url-formatting
I can use:
#+INCLUDE:
to include an org file in another org file, which allows me to assemble, say, a website from various org files. I'm exporting from the C-c C-e exporter in org-mode 7.5.
I could maintain a quite complex publication this way. This modular approach is quite common in, e.g. LaTeX and Texinfo publications.
However, links to images no longer work from the #+INCLUDEd org files. What seems to be happening is that the path to the images is taken as being from the org file that I am exporting from, rather than the actual org file that references the image.
The only ways I can see to resolve this are to:
use a flat file structure; or
make the image path from the referencing file (which I might not know in advance) rather than itself.
Neither of these is really sustainable.
How do I tell org to use the correct image path from its own relevant org file rather than the parent org file?
From what I know of the exporter, INCLUDE files are inserted into the document before export. Therefore the content is part of the document before it starts following paths to reach any links to files (images).
After a bit of testing you likely will need to use absolute file paths. Since you move between Windows and Linux your best bet would be to use a consistent scheme on both starting from your home directory.
Like that you can make the Org link:
[[~/path/to/image.jpg]], which will work on both systems (assuming you have set %HOME% on Windows).
Option 1 is potentially an alternative (although I agree it wouldn't be ideal at all), whereas the second option would have obvious pitfalls if you INCLUDE the file in more than one future document.
My situation is the following:
I have an index.html and some JavaScript that loads HTML snippets from the server. Inside these snippets, I have some URLs to images like
/some/folder/picture.jpg
Of course these do not work in PhoneGap. Weinre tells me that PhoneGap is trying to load the picture from
file:///some/folder/picture.jpg
Any ideas how to solve this? I was thinking about something like a base href, or some configuration in PhoneGap where one could specify a root path, but I did not find anything like that ...
Thanks,
Michael
I had the same problem especially when you have a lot of views (pages) and want to load one from a menu, yet you are at an unknown location.
The simple work around is to use the window.location object.
window.location.href.split('www')[0] + 'www'
This gives you the absolute URL to your 'base'. The www is the folder which is relevant for IOS and Android, so this also makes your app compatible in multiple platforms.
From this you can use a regular expression which passes the entire doc like jquery mobile does with data-* attributes to describe their elements. You simply replace the regular expression with the path returned. You'll want to do this during initialisation otherwise it will create a massive bottle neck.
Hope this helps and is along the lines of what you're looking for.
Cheers,
Sententia
You can't do that with a <base> because / is always host-relative — it can't be redefined to be in a subdirectory. You have two options:
rewrite your HTML to use fully relative paths like ../../some/folder/picture.jpg (or have something do the rewrite for you as a build step), or
alter the "browser" (PhoneGap's wrapper) so that it loads URLs differently.
I'm not familiar with PhoneGap so I can't comment on automatic options, but I personally would start using relative URLs.
I have an ASP.NET MVC2 application where I need to support not only multiple languages, but also potentially multiple versions of each language. I usually solve localization requirements by using resx files in the App_GlobalResources folder, and this works well as long as I do not need to support multiple resource-sets for the same language.
This is an issue because each customer shall be able to specify a set of resources, and they may use the same language.
My initial thought was to have a file structure where every customer has a separate folder located under for instance App_Data. In this customer folder I would put configuration files and resources. But then I would need a way to tell the application that it should look for resources in this particular folder instead of App_GlobalResources.
So my question is: Is this doable, and what do I have to do to make it work? Is this a bad way to solve a problem like this, and if that seems to be the case: Does anyone have suggestions for a better solution?
Will be thankful for all input.
I usually use a custom ResourceProviderFactory to store the resources in the database. Creating a custom provider to look in specific folders should not be to hard if you can distinguish the different customers by virtualpath.
But then I would need a way to tell the application that it should look for
resources in this particular folder instead of App_GlobalResources.
You might consider compiling your resources so that they are deployed as DLLs rather than compiled at runtime. To do this you have to move your resources our of the standard App_GlobalResources.
This post has a good explanation of the benefits of doing this:
http://odetocode.com/Blogs/scott/archive/2009/07/16/resource-files-and-asp-net-mvc-projects.aspx