Recently had a customer on Small Business Server think someone might be logging into the server as him. To check logs in IIS for a user :
2 ) Copy the logs from the default Location
3) Save the following as query.sql in C:\Temp\Logs\
SELECT cs-username, date, time, c-ip, cs-uri-stem, cs(User-Agent) FROM C:\Temp\Logs\*
WHERE cs-method LIKE ‘%get%’ and cs-uri-stem LIKE ‘%owa%’
Logparser.exe file:C:\Temp\Logs\query.sql -i:IISW3C -o:CSV
File Zip Download :
Looks like the main scrapers I found are Import.io and Octoparse
import.io gives you a free 7 day account with 500 Requests
- ) Get a list of all products
Navigating around the site it looks like all their products are put on pages like this : https://www.ikea.com/au/en/catalog/categories/departments/outdoor/17893/ so we need to find a list of departments and their , Ikea actually list them here : https://www.ikea.com/au/en/catalog/allproducts/
Enter this URL in an import.io extraction service
- Create a new extractor and enter one of the products pages then choose the Edit and select the products images and other info
Now use the other extractor from Part 1 as an input to part 2
- Install : Xdebug
Can be done by install then entering the following : /etc/php/7.1/fpm/php.ini:
zend_extension = /usr/lib/php/20160303/xdebug.so xdebug.profiler_enable = 0 xdebug.profiler_output_name = cachegrind.out.%t xdebug.profiler_enable_trigger = 1 xdebug.profiler_output_dir = /tmp xdebug.profiler_enable_trigger_value = "<super secret key>"
In order, the configuration goes as follows: load the module, disable profiling be default, set the filename, enable triggering via GET/POST parameter, output in /tmp and only profile when given the key.
Restart php-fpm and you should be good to go.
2) Use the ?XDEBUG_PROFILE=<super secret key> appended to any page you want to debug and the debug file will be put in /tmp.
3) Open the debug file using something like : https://github.com/jokkedk/webgrind For Analysis specifically for reducing
Invocation Count is how many times that function was called. A simple tip for reducing this is to pull out any repetitive function calls from a for-loop into a single variable.
Total Self Cost is the total percentage or time that the function is responsible for. You can improve this by reducing code complexity, using built-in native functions or removing unused variables.