I'm running POSTMAN sync (sync data across devices) behind a network proxy and it is not working. Apparently it's not honoring the global proxy configuration in my system. Login in and upload is working fine. Only the sync has the issue.
I'm using
Ubuntu 14.04 LTS 64bit
Chrome Version 47.0.2526.106 (64-bit)
Postman version 3.2.9
I have also tried restarting and reinstalling POSTMAN with no luck.
The most likely cause is that your proxy does not allow websocket connections that Postman sync uses for data synchronization. Check for error messages in Postman's DevTools window
Here is a good description of how to debug this issue.
Related
After upgrading Tomcat on windows, Chrome is not able to pull some files. It seems to fail when running scripts using relative paths. Some small files return fine.
Chrome console:
net::ERR_CONTENT_LENGTH_MISMATCH 200
Problem persists when trying several newer versions of Apache Tomcat.
For the record, I have also changed my appBase. Problem seems to persist either way. Default Tomcat content serves fine.
This can be solved by opening the Tomcat Service
Properties
Log On
Select local system account
Allow service to interact with desktop (not sure this is needed?)
And is explained fully here Tomcat Service gets installed with “Local Service” account
I'm using BurpSuite to intercept the HTTP/HTTPS requests sent when logging in on https://www.nike.com/. I'm trying to achieve this with the following step:
Opening BurpSuite and Firefox
Turning on the proxy intercept
Turning on FoxyProxy on Firefox
Opening the website and trying to logging
These steps usually work for me, but in this case, I'm getting a "we are unable to connect to our servers" error without anything appearing on the intercept tab when trying to logging (I have tried turning off the intercept feature but it still yields the same issue, so I think it might be a proxy and certificate problem).
To clear things up:
I'm running the latest versions of BurpSuite and FireFox.
I have installed and reinstalled the BurpSuite certificate using this guide.
I've tried all of this on my iMac, MacBook and iPhone all of these devices yield the same issue
Here bellow is the error message I'm getting:
Here are my BurpSuite Proxy setting:
(in the Certificate tab I just have Generate CA-signed per-host certificates selected)
I have been using BurpSuite for over 2 years now and it's the first time I'm facing such an issue, any help is appreciated
I have shared my question with the Portswigger support (the team behind BurpSuite) and got the following response:
Hi
Thanks for your message.
We have reproduced the issue in our testing environment.
It looks like Nike.com are performing a fairly sophisticated check to
stop automated tool from accessing parts of their site.
Please let us know if you need any further assistance.
Cheers
Liam Tai-Hogan
PortSwigger Web Security
I’m having an issue with the spring boot dashboard. When I start an app the icon show the loading icon and never reaches the green up icon though the app does start and accepts requests. When I stop the app it takes a couple of minutes to stop.
I have access to another machine where the dashboard behaves as expected.
I’m using the getting started rest service app (gs-rest-service-complete) targeting spring boot 1.4.3.release with no modifications. I’m using sts 3.8.3.
I’m experiencing the issue on OSX El Capitan 10.11.6
My jdk version is 1.8.0_112
I've found a couple of similar questions but the suggestions don't resolve my issue.
This one relates to bad entry in hosts file - mine is ok (Spring Boot Dashboard projects never finish starting)
This one suggests switching life-cycle-bean support off, but I want to know how to use run the dashboard with it enabled. The response to this question also requests a sample app, as stated I'm using the gs-rest-service-complete sample app (STS Spring Boot Dashboard Doesn't Recognize Successful Start)
What might be causing this problem?
It sounds like the machine where it doesn't work might have some kind of firewall stopping the JMX connections. These connections are made via sockets. Firewall type software sometimes prevents the connections. If you know of firewall type software running on your machine you could try disabling it or (less drastically) trying to reconfigure it so it allows connections between different processes running on your machine.
I'm running JMeter 3.0 on a laptop (Lenovo y700) with win10. I'm trying to get a response from a website and getting a 404 response. when I try other web sites everything works fine. tried running it from my desktop PC (win 8.1) but got the same 404 , and with another website, everything runs fine. now here's the tricky part. I've tried it again on a mac laptop (not sure the version of the os) and there everything was running fine (including the website who didn't work on the other machines).
1
3
Try using SOAP/XML-RPC Request with Send SOAPAction enabled and one HTTP Header Manager in the request.
Apache Jmeter - Samplers - SOAP/XML-RPC_Request
Look at your website logs. It is unfortunately common for developers to leave a reference on a web page which is not built out, leaving an orphaned reference. if you see the 404 in the HTTP request logs and in your results then you can be objectively certain that the reference is missing.
Should have been caught by development but was not
Should have been caught by functional testing but was not
Test blamed for being faulty because it reported something no one else caught
Common scenario....
I'm using XCode 4.0.2 to upload my iPhone app to the iTunes app store but get the following error messages:
Failure instantiating web-service client
An exception has occurred: Unable to open url: https://contentdelivery.itunes.apple.com/WebObjects/MZLabelService.woa/ws/MZITunesProducerService?wsdl
Could not connect to Apple's web service
Unable to authenticate the package: 450416349.itmsp
I've got the latest Java version (1.6) and have double checked the network settings in the Java preferences.
Any ideas?
Got to the bottom of it. Running a TCP dump on our firewall discovered that some (but not all) of the requests that XCode made were using the configured proxy, and others were not.
We allowed the proxy to be bypassed completely to test and it all worked fine.
Have you tried using Application Loader? Try that and see if it works. Hope this helps.