I have a tool retrieving RSS feeds. To test, I was using http://rss.cnn.com/rss/edition.rss .
While the browser is able to retrieve the feed, by tool was getting a 404.
I noticed other RSS tools that failed with the same error.
Investigating the WireShark logs, I noticed that the difference was that my tool used Host: rss.cnn.com:80 while the browser used Host: rss.cnn.com.
And indeed, removing the port completely fixed it.
But what does it mean?
Related
I want to send a POST request with a body in WSO2. actually, I have a Django rest framework with some APIs and want to send requests in WSO2 API manager. it's all OK for GET, DELETE but when I want to POST some request I'll receive a bad request from Django server.
Django server is running on http://localhost:8000/user-api/users/
in wso2 api publisher api's URL is : http://localhost:8243/users/1.0.0
endpoint in wso2 is : http://localhost:8000/user-api/users/
the below picture is what I receive when I send GET request:
I send POST request with this json as body:
and here is what I receive when I send POST request:
Everything is ok when I check the server's URL in my browser.
UPDATE:
when I use my Django server as a gateway for WSO2 everything is OK but when I use default WSO2-Gateway everything goes wrong.
I'm not clear about what this question is really asking. But I feel this is generally asking how to debug this situation. I apologize if I got that wrong.
To start debugging a problem with a WSO2 server in the mix there are some common things to think about:
If this is a local or development region can I use http, instead of https, so that I can view things as plain text during debugging activities.
For the Enterprise Integrator products there is a test feature for back end endpoints in the admin Console. This can often be helpful to ensure communication can happen. It's like a simple ping.
Check inside the trace.log to see if there is anything helpful for you.
For APIM use the Test a REST API feature to try out the backend to see if that works before coming in the front door of the server.
For WSO2 products if reviewing logs aren't giving enough information then you can use the Wirelogs to enable you to view every piece of information that goes in and out of the WSO2 server. These are formatted roughly like Wireshark logs but the output is inside of the wso2carbon.log file. The key here is getting used to the >> and << to determine if the log entry is going out of or into the WSO2 server.
If you still can't find the issue then you might need to go down to reviewing the data as it goes across the wire. This is a bit complex at first but you'll quickly get the hang of it. (Hint: This is extremely helpful for trouble shooting JMS communication.)
On linux you can use tcpdump to write data to file and then open it with Wireshark. Windows has a similar system.
For tcpdump you need to use the interface name. It's often like eth0. You can find t using ifconfig. It's the value: before the flags.
Example tcpdump capture:
tcpdump -s 0 -I {interfacename} -W 30 -C 50 -w wsoei-01-07192022.pcap -Z root
tcpdump -s 0 -i ens192 -W 30 -C 50 -w wsoei-01-07192022.pcap -Z root
Once you have the pcap file captured you then use Wireshark to open it. And there you have it you can see everything that went across the wire. Once you have that you can start to see at what point things are breaking down.
Conclusion
If you zoom in close enough with your research you will eventually find where the breakdown is.
I am running a Django project with react redux (trying to implement authentication system) and the very weird thing i observed that my site is rendering properly when i use localhost:8000 or http://127.0.0.1:8000.
But when i m trying to login/signup (ie trying to send post request) then it working only when i use localhost:8000, and giving some error when using http://127.0.0.1:8000.
One of the error when using http://127.0.0.1:8000 is shown below.
However i have seen this and found localhost will often resolve to ::1, the IPv6 loopback address. But i am getting is it related to this or not ?
And whether localhost:8000 and http://127.0.0.1:8000 is same or not ?
Please try to answer in simple words because I have not much knowledge of internet protocol or networking.
This problem is because of CORS. You have to enable from outside your application.
This happens because django apps and generally all frameworks blocks requests outside your address.
You can read more about CORS here
We have recently started experiencing problems with communication with our ESXi devices through CIM, TCP port 5989. At first we thought this was related to our remote monitoring and maintenance tool, N-central by SolarWinds N-able, however we now have reason to believe that this is not the case.
The reason for why I believe this is a Vmware is that I've attempted to reach one of the ESXi devices at 5989 by browsing to it with Internet Explorer. These attempts have all resulted in the HTTP error message 501/505 Not Implemented.
I have already attempted to browse to the page with HTTP 1.1 both enabled and disabled in Internet Explorer, no change. I've tried with and without compatibility view, no change. I've tried Google Chrome, I only get a blank page and when I check the response from the server Google Chrome just says "Failed to load response data."
Is anyone able to assist me in figuring out what is wrong, and fixing the error(s)? Please do let me know what information is required to best troubleshoot this issue.
I may misunderstood of your question;
the port 5989 descripted here in vmware website:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2039095
vcenter server should access the esxi host with this port(CIM XML transactions over HTTPS), the error code 501/505 means that the esxi host did not recognize your client(which you use browser try connected to).
if you can pretend the agent to be vcenter, I guess you can fix the problem.
that's my first question here. After long research, I decided to ask for help...
So first I'll explain my scenario. I have some SOAP web services here. They're consumed by an .Net website. The .Net framework used is in version 4.0.
So my web services are configured to accept HTTP/1.0 protocol, due to .Net limitations. In spite of that, everything works fine if I access the service directly to Jboss AS(4.2.2 GA).
But, I have to make it work with Apache web server as the receptor of the request. Apache do a inverse proxy redirection to my service, so the site send requests to port 8080 (that Apache is listening) and send it to jboss that is expecting the request at port 18080.
In many tests, I confirmed that almost every service worked almost fine, sometimes they have the same failure. But one in particular don't work anyway, the request stopped at Apache with status 400 and empty value (the - after the 400) like that:
POST /xxxx/xxxx/xxxxx/MyService HTTP/1.1" 400 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Service Client Protocol 4.0.30319.296)
The other requests that are processed have this value filled. I guess is the response size.
Please consider my regards. thanks
After great efforts at my company we discovered using an Sniffer(Wireshark) that we had two problems that let us to had the situation described in this problem.
First problem solved: .Net platform is configured to send by default an empty request. The first attempt failed so .Net was forced to automatically send a second request with authentication. So i figured out 2 requests before the Jboss response formed an http 400 error.
Second Problem solved:
After the other side solved thise previous problem configuring .Net properly, we tested again and the results were conclusive that no more requests was hitting Apache Http Server. - So there was a strong signal that we had something blocking this specific service. With the rocks in my hand, infrastructure people started to move their asses and somehow solved the problem. Mine frustration in the end is that they didn't said nothing about the possible correction. So "suddenly" the communication was restored..
So after all we made it! but with a bitter taste of defeat. Thank you all that supported me in this problem. []s
when i try opening http://127.0.0.1:8500/test.com
I get
500 There is no web application configured to service your request There is no web application configured to service your request
when i try opening http://127.0.0.1:8500/CFIDE/
I GET THE same error
Kindly guide me to solution.
It means the server did not fully start. The JRun container started and was able to accept an HTTP Request via its internal webserver port, but then the ColdFusion Server inside JRun was not fully deployed or not deployed at all.
The startup events in /path/to/coldfusion8/runtime/logs/coldfusion-event.log and /path/to/coldfusion8/logs/server.log will contain details about what failed during ColdFusion startup.
You will probably not make sense of the events as they are usually somewhat cryptic. Please post log contents for further diagnosis.