If you consistently get redirected back to the login page, my first guess would be that your browser is not accepting/storing the cookies sent after login (assuming the user and password are correct). Have you looked at what cookies a successful login sends in the response, and whether your browser stores these cookies?

This has very little to do with Perl and without you posting the relevant code and finding out what in the environment has changed, we likely can't help you further.

Can you show us the Perl code that is failing?

Heh https://web.archive.org/web/20160603184558/http://tetrabb.com/

If this worked fine up till now then there could be some underlying issue to do with resources on your system. You don't say if the app or server logs provide any details, and you don't provide the code which you have (that we don't). The last release of this software is from 2013, the archive.org link provided doesn't have an archive of the software. How do I post a question effectively?, tutorials->Debugging and Optimization.

Hello yedsai.

Can't say I have ever seen a landing page with a .pl file extension before, so that is a little ominous from the getgo. Not to say it is wrong, just unusual. I would expect either a .cgi or .*ml extension at that path.

I am currently attempting to determine whether any user should be landing at any path involving cgi-bin, as opposed to a .index extension at the Public_Html directory. Though I don't seem to be able to set permissions such that any user should not be allowed access the cgi-bin path whilst also allowing the website to work as normal.

I am definetly interested in the outcome of this one.

.pl isn’t completely unusual. Extensions for web apps are just a matter of configuration—telling the webserver which extensions to execute—or application routing—setting your app to do something based on any valid URI path. They are convenient in the FS but should never be trusted–

mv pwnMachine.exe kitten.jpg
[download]

Your Mother, of course, in the last few days I have been doing some admin at my webhost and up popped some .pl extensions, followed by key=value params. Thereby instantly contradicting myself. Not meaning to go OT from the main question, as I have similar niggles with understanding how to approach my $worktime interfaces.

Most likely it is a configuration issue, but then we like to look at where is the line between what is the issue in terms of being perl related. Server configuration is not necessarily a perl issue in of itself, but at least in regards to transcribing web documents, being part of a community that can share the info is almost, if not as, important.

Regarding the code snippet you provide here. I think this is one of the things that might help progression with learning the language, just saw Coding in Perl? What support do you need? as I logged. That is, miniature examples of the kind of security issues that we would rather not unintentionally reproduce. But now I am going ot.