I.e. the idea is to use a URL like file:///path/to/download/location/update.xml.
Are there any gotchas if we go that route?
Yes, it's possible to do that, HTTP is not a requirement.
Related
I'm exporting an express app called eggman with webtask-tools.
My res.redirect('/walrus')ses don't work.
The url for my app is ….sandbox.auth0-extend.com/eggman/walrus, which means / will point to ….sandbox.auth0-extend.com/walrus instead of /eggman/walrus.
Is there an elegant way to set a basepath to all redirects?
The hack is to use res.redirect('/<webtaskName>/path'.
I've sent a PR to address this at the library level but I don't expect them to implement it.
I'm new to Perl and to Active Directory.
I need an example code of connecting into
an Active Directory server
(only address, there's no need to login),
and fetch all the details of a user by id.
I've searched the net and found script only
with the use of Net::ldap, but I am forced
to use Win32::Ole. Could someone please help
me to get it right at this way?
The best way is to use Net::Ldap. If you are not able to do so then the second best approach is to use some kind of Windows tool (like ldifde.exe/csvde.exe) and parse its output.
Basic usage: http://ss64.com/nt/csvde.html
More on ldifde: http://blogs.technet.com/b/lifeofapfe/archive/2009/02/19/using-ldifde-to-export-users-from-active-directory.aspx
Regards,
Please suggest how to use the composer. Is there a way I can just input a file with a list of URLs and have fiddler check those links for me ?
There's no built-in feature that performs exactly that function, but you can easily write script that does this. Use the utilIssueRequest method on the Proxy object to send a request to a target URL. See http://www.fiddler2.com/fiddler/dev/scriptsamples.asp for a full script example.
I want to include the distance_of_time_in_words method in a sinatra app
I don't want to package and distribute a gem, which is what the Sintra docs direct you to do. I just want that method accessible in my view.
What's the easiest way to do this? Thanks.
On http://www.sinatrarb.com/intro.html look at Helpers section and define helper methods for use in route handlers and templates
Just place the file somewhere in your ruby load path ($LOAD_PATH) and require it. Or place the code directly in your app file.
I'm very new to Perl, and I have absolutely no idea how to approach this. We have an old Perl application which previously used Apache auth; we'd like to replace this with a cookie based form-style authentication. I understand that this is very case-specific, and there is no one answer as such, but some general tips would be much appreciated.
Will I need to edit all .pl files in the website? Or is there a "golden hammer" solution I can use? Is there something on CPAN I can use? We're using Perl v5.8.8 if it matters, and we're using Apache 2 shared hosting. I am happy to provide additional information as is necessary.
For the authentication to be recognized/required, it will need to be checked by the .pl file that initially receives the user's request. So the answer to whether all .pl files will need to be changed depends on how your application is structured:
If the user goes to http://myserver.com/one.pl to do the first thing and http://myserver.com/two.pl to do the second thing, then, yes, you'll need to change them all because they're all receiving requests individually.
If the user goes to http://myserver.com/dispatch.pl?mode=one for the first thing and http://myserver.com/dispatch.pl?mode=two for the second thing and dispatch.pl calls either one.pl or two.pl behind the scenes based on the mode parameter, then you only need to change dispatch.pl, since it's the only one directly receiving requests from the user.
Edited to add: If you're dealing with the first model, then I'd strongly recommend setting up an external module (.pm file) with the cookie-handling code and calling that from each of your individual .pl files instead of duplicating that code all over the place. Ideally, this would let you get by with only a few lines of added code in each .pl:
use MyCookieHandlingModule qw(verify_cookie redirect_to_login);
my $q = CGI->new; # ...unless you're already using CGI in object-oriented mode
redirect_to_login unless verify_cookie($q);
You could do it at a level outside the Perl program.
Thanks for your answers guys, but I eventually decided on CGI::Session::Auth::DBI which works well on shared hosting.