Recently I started using SmartMeter. Everything seems to work fine for other requests, but if I try to use the HTTP request sampler to test a PUT request the request body is not visible in the request:
<actual file content, not shown here>
Now I've searched the internet and it seems this was an recent issue with JMeter that should be fixed in v3.1, is this the same issue in SmartMeter and how should I be able to fix it?
Greetings!
I assume you are referring to this issue https://bz.apache.org/bugzilla/show_bug.cgi?id=60092. It has indeed been resolved in JMeter 3.1. Use SmartMeter 1.3.0 or newer.
Related
When implementing a RequestMock in TestCafe does the original request still get made and completed and then modified by TestCafe or does TestCafe intercept the request and stop the original?
I'm asking because we are thinking about using this feature to mock some requests to speed up testing, such as mocking images. However, if the original request still has to be completed before the mock then this does not seem like a viable solution.
RequestMock intercepts requests to a web resource and emulates a response, so the original request is not performed. Please refer to the documentation for more information.
I've created a pipeline trigger in Gitlab as the documentation said, but when I open it I get a "error": "404 Not Found".
Webhook URL: https://gitlab.com/api/v4/projects/xxxx/ref/xxxx/trigger/pipeline?token=xxxx
xxxx is being replaced by the values I have. Tried different things, setting the project to public. Enabling/disabling Limit CI_JOB_TOKEN acces.
I'm a bit lost right now.
As examples show you need to use http POST method
curl -X POST $WEBHOOK_URL
If you are pasting the URL directly to your browser it will use http GET and result in 404 error.
The feature that you are referencing in the question might not be working due to a GitLab bug that was introduced in 12.0.0. Please see the issue here: https://gitlab.com/gitlab-org/gitlab/-/issues/30486
I’m trying to get and print the HTTP protocol version of the target in requests made by vue-resource in a Vue.js component. I don’t have any problem in getting headers like Data or Server: being on localhost I use a proxy to bypass the CORS limitations as well, but I can’t figure out how to do the same with that. As far as I know, both Chrome and Firefox developer tools refer to the HTTP protocol version in the request (not in the response), so using response.headers.get("foo"); as explained in the official documentation doesn’t work, and I don’t have a request variable set. I just need to show if the target uses HTTP 1.x or 2.x in a string like HTTP/1.1 200 OK — I can’t understand if Vue.http.interceptors could help and how. I guess it shouldn’t be that hard… thanks in advance!
EDIT: Unrelated to Vue.js itself, but resource.nextHopProtocol did the trick — on Firefox, at least. Being a Candidate Recommendation, it doesn’t work with all the browsers.
The code is as simple as
this.$http.post(url, data);
On local machine it generates POST request.
On cloud server it generates GET request.
Version of vue.js is the same.
On localhost request to /example/url/ is processed without redirect but on server request to /example/url/ makes redirect to /example/url (without trailing slash). Because of this POST becomes GET.
I faced this same problem. try to use [HttpPost] attribute in the controller along with the attribute you are using.
Some of my site users are unable to call any api endpoints successfully whether through AJAX or a direct GET request in the browser. All HTML pages work fine. They get the following error when hitting an API endpoint.
--
--
What can be the issue here? I am suspecting some kind of firewall/ISP/Network restriction may be causing this, but I am not sure. What can I do to debug the issue? I checked my server logs and the request is hitting my server and the right response is being sent back. I am using rails 3.
UPDATE
Figured out the issue. The client's firewall is blocking application/json content.
The client's firewall is blocking all content of mime type application/json