I have a Canvas Facebook App which has a developer version(for test & dev purpose) accessed through localhost and a staging version deployed to Heroku. Whenever I try to access the developer version through localhost, I get the following error:
[2013-02-24 17:43:40] ERROR bad Request-Line `\x16\x03\x01\x00│\x01\x00\x00»\x03
\x02Q*ѼX\x0EÑ÷╫┤EΩa▀f⌠├÷RNu#N╕╨6$╙iRZ╛\x00\x00H└'.
[2013-02-24 17:43:40] ERROR bad Request-Line `\x16\x03\x01\x00│\x01\x00\x00»\x03
\x02Q*Ѽπ'k1w3Ää¿\x10ëσÅú├\x18$Æë{«ÄNù▐\x03$D\x00\x00H└'.
[2013-02-24 17:43:40] ERROR bad URI `!]è"!┼I\x00\x00H└'.
[2013-02-24 17:43:40] ERROR bad Request-Line `\x16\x03\x00\x00U\x01\x00\x00Q\x03
\x00Q*Ѽ╦▐σ\x12╥N\x7Fi+∩£\x1Dcúë[1/°╡½ñV é₧·Y\x00\x00*\x00 \x00ê\x00ç\x009\x008\
x00ä\x005\x00E\x00D\x00f\x003\x002\x00û\x00A\x00\x05\x00\x04\x00/\x00\x16\x00\x1
3■ \x00'.
I have no problem accessing the staging version in heroku. To make things more interesting, my co developer does not have this problem when he tries to access the app through localhost. We are using the same environment(Windows OS and webrick server). I am suspecting the problem is with my account, but I have no idea how to verify/fix it.
Try accessing clearing the cache.
I was getting the same error while accessing api using https having config.force_ssl = true, but its working fine with http request.
Related
during pentesting SOME site I have faced with file upload errors. It is 403 error Forbidden but the most interesting thing lies in the fact it is happening ONLY when I use burp proxy.
When I am uploading passport/id document as a usual way(withou Burp Suite) - No error. 200 OK.
When I am uploading with Burp Suite - 403 Error.
P.S.: Other site functionality/APIs work properly when I use Burp Suite
I have no idea why this 403 error occurs. Is this a bug or a kind of "protection"?
Then you don't have the authorization to set up a proxy in your OS.
I guess you are using your corporate laptop. Try to change you network settings in your browser. If they are grey out then your organization has blocked that for you ( Bgroup rules).
I faced the same issue exactly and this was the problem.
Hope that helps.
I was trying to run a junit,which calls an API (https:conectapitest.company.com/consumerservice/createConsumer) ,when I was running using eclipse neon (java8) I am getting the following the error .
Unexpected response from Connect server: responseCode=403, responseMessage=Forbidden responseBody=<html><body><h1>403 Forbidden</h1>
Request forbidden by administrative rules.
</body></html>
The API is working when I run in postman. I am using Mac OS. Is this issue related to eclipse or MacOS?
I verified all eclipse configs ,did not change any settings ,it worked few weeks back.
while running the testcase, I noticed the message like
SystemProperty java.net.useSystemProxies = null defaulting to FALSE
How to fix this issue?
When i use the CallClient of #azure/communication-calling SDK to create a CallAgent, i'm getting 'No CommunicationTokenCredential provided' error even though i'm passing a valid CommunicationTokenCredential
Ex: this.callAgent = await this.callClient.createCallAgent(tokenCredential);
I'm able to successfully deploy a standalone react app & run the following sample application and make a web call as suggested in Microsoft docs. https://github.com/Azure-Samples/communication-services-web-calling-tutorial
But, when I integrate this into my existing React App, I start having issues in creating a CallAgent with the following error:
'azure:ACS:error 27/10/2021, 18:13:48:96 CallClient1:CallAgent1 op:Initialize failed, message=No CommunicationTokenCredential provided,'
I am passing the CommunicationTokenCredential properly while calling the createCallAgent(token) (verified by printing the token as well).
But still, I get this error. Has anyone else faced this issue?
This seems to be on a very new topic because the "stitch" or "mongodb-stitch" tags do not exist yet.
I have a mongodb altas cluster on cloud.mongodb.com. The page https://docs.mongodb.com/stitch/auth/email-auth/ only teaches how to do things with JS but I don't have server side JS on hand. Instead I tried to figure out how to do things with the StitchClient on the Android API.
I was able to register an email/password pair using StitchClient.register(email,pwd) and got an email from no-reply+stitch#mongodb.com with the token/tokenId. I copied them and used StitchClient.emailConfirm(token, tokenId) but failed. The error was:
Unexpected response code 404 for https://stitch.mongodb.com/api/client/v1.0/app/APP-ID/auth/local/userpass/confirm
which sounds strange! I opened a browser and paste that in the URL and got 404 too. I even did
curl --data "token=432...345&tokenId=435..334" https://stitch.mongodb.com/api/client/v1.0/app/APP-ID/auth/local/userpass/confirm
and still got 404.
Is this a bug or an outage of the stitch.mongodb.com server?
I'm trying to get the latest version of an artifact.
going to http://archiva:8080/restServices shows me the Available RESTful services: clicking on http://archiva:8080/restServices/archivaServices?_wadl leads to an empty(all white) page fore me. Opening the Development tools in my browser I get this output in the javascript-console
Failed to load resource: the server responded with a status of 404 (Not Found)
and
GET http://archiva:8080/restServices/archivaServices?_wadl 404 (Not Found)
I also read here that there should be a application.wadl but for me there isn't!
I use the latest(2.2.1) Standalone version from here
the request for a certain artifact looks like that
http://archiva:8080/restServices/archivaServices/searchService/artifact?g=eu.test&a=test&v=LATEST
Maybe you miss the contextPath in the url. For example, if you want to access the ping service. The url could be:
http://localhost:8080/archiva/restServices/archivaServices/pingService/ping.
Please notice that maybe you will get 403 due to by default archiva does not allow csrf access.
The configruation detail is: http://archiva.apache.org/docs/2.2.3/adminguide/customising-security.html