%% Last Updated: - [[2021-02-10]] - [[2020-12-04]] Related - [[JMeter]] [[Load Testing]] %% ## Parameter not parsed in request ### Problem There's a parameter in the HTTP request that isn't being resolved. For example, `${viewState}` remains as that literal string. This can hold true for a GET or a POST. ### Solution Check to see whether you've properly ended all your parameters. One thing I kept doing is forgetting the closing parenthesis on `${__time(dd/MM/yyyy)}`. Closing the parenthesis correctly should cause all parameters to be parsed on replay. ## Sampler uses succeeding sample details ### Problem When replayed, a sample does not use the URL provided in it; instead, it uses the URL and details of the sample after it. ### Solution The first sample is automatically redirecting to the next sample. Untick "Follow redirects" on the first sample to stop this behaviour. ## Unable to record ### Problem The site cannot be recorded in JMeter. Example: While attempting to record a login, the login does not complete. ### Solution Make sure that the HTTP Client 4 is selected in the HTTPS Recorder. ## [[JMeter/XPath Extractor]] ### Problem Error: `Prefix requires namespace (rdf).` ### Solution Tick "Use namespaces" in the XPath Extractor. ## Authentication not working ### Problem Despite the request and response being exactly the same, login does not work and the error message says that the user is not permitted to access the resource. ### Solution JMeter sometimes doesn't record cookies even when they are there. To solve this, add an HTTP Cookie Manager et voila! ## JMeter can't record HTTPS ### Problem No HTTPS traffic is recorded. ### Solution - Go to apache-jmeter-3.1/bin. - Double click on ApacheJMeterTemporaryRootCA.crt. - Click Install Certificate. - Put the certificate into your Trusted Root directory.