Does step load work in last locust versions (2.4.3)? - performance

Is it possible to do step load on Locust version 2.4?
Link from this page https://docs.locust.io/en/1.2.3/running-locust-in-step-load-mode.html redirect to 404 page.

The page is just renamed. Here's the latest version https://docs.locust.io/en/stable/custom-load-shape.html

Related

TYPO3 6.1 + macina_banner 1.5.3 : Redirect fail after migration to HTTPS

TYPO3 6.1 + Macina banner
macina_banners 1.5.3
Tested on Chrome and Firefox
I use EXT: macina_banners to display banners
Everything was working fine until I switched to HTTPS.
After migrating to HTTPS, redirect stop working
Since I changed to HTTPS, a click on the banner reloads the same page, and redirect does not work.
When I am logged in TYPO3 backend, when I click on the banner it still reloads the same page, but if after that I reload the page with ctrl+MAJ+R, I am redirected to the target page.
If I reload the page with ctrl+MAJ instead of ctrl+MAJ+R, it just reloads the same page with no redirect.
I am a bit confused because It looks like a cache issue, but the problem appears only with HTTPS, and everything works fine with my dev website which is HTTP.
I have checked the ext code, I didn't find anything (but I am not a php expert).
I have deleted the content of typo3temps, it didn't solve the problem
Any idea what could be the problem or where to investigate?
Summary :
Not logged in the backend
When reloading page with ctrl+R, reload the same page: KO
When reloading page with ctrl+MAJ+R, reload the same page: KO
logged in backend
When reloading page with ctrl+R, reload the same page: KO
When reloading page with ctrl+MAJ+R, load the target page: OK
Please Update TYPO3 version 6.1 does not get any security updates. This means you running an security risk. And might be liable. And my guess not many active community members are able to help you as your versions are ancient

404 page not found codeigniter version 2.1.4 running on hostgator

My site has been running for years and I used codeigniter framework version 2.1.4. Until yesterday everything was OK.
But early this morning i started getting this error
404 Page Not Found The page you requested was not found..
What might be the problem? Capitalizing first letter of the controller files and class names hasn't helped
to get more information about your errors use following in index.php file in project root directory
case 'production':
ini_set('display_errors', 1);
now post your error description here to get the solution
(you will find this code block in switch (ENVIRONMENT))

Joomla configuration page next button not working

joomla configuration page
I want to learn how to use joomla but the problem is that i can't continue from the first page is just keeps on validating the fields even though that have data, your response to this request will be highly appreciated.
Not sure what version of Joomla but make sure you are meeting all requirements for that particular installation. It could be something like an unsupported version of the PHP version which I have come across in the past.

Codeigniter 2.0.2 built-in caching is slower than 1.7.2

I'm not sure with the built-in web page caching in CodeIgniter 2.0.2 I am using.
I just upgraded my CI version from 1.7.2
It did not have any problem at all before, the page loads really fast.
but it takes the same to load the cached page, after it is cached on CI 2.0.2
I already checked the file has been created in /application/cache folder after the page load.
It seems like it doesn't load the cache file.
Anybody has the same problem?
How can I solve this?

xajax and codeigniter - blank page and xajax request URI error

I am unfortunately getting a blank page when trying to run a site locally. There are other people running it locally just fine, so I am wondering if it could be something to do with my LAMP environment.
When I attempt to load the site, it's nothing but a blank page. I've ran php index.php in console and the error I get is the following "xajax Error: xajax failed to automatically identify your Request URI.Please set the Request URI explicitly when you instantiate the xajax object.". I'm not quite sure how to handle this in CodeIgniter and or at all to be honest.
I think it's a problem with LAMP configuration: check codeigniter folder permissions (add write permission to "logs" folder.
Thanks for your answer. I actually figured out what the problem was, it was like you said a problem with my LAMP configuration. Unfortunately XAMPP (which is what I am using and or was), the newest version uses PHP 5.3. Xajax doesn't support PHP 5.3 and this was causing the problems. After I went to an older version all was well!

Resources