Is there a setting or a work-around for me to stop GraphQL queries from being displayed in browser developer tools? In Chrome, my GraphQL queries are listed under the "Payload" tab in the "Network" section. It is a full query that works if I copied and pasted it then sent the request using Postman or in the Playground with the right data.
When I check FaceBook, I don't see a full usable query written out. The shape is not visible.
Related
Ok so I have got this weird error. I am passing user credentials via postman.
In one tab, I am getting an error, but when another tab is used it works.
As far as I have checked everything is same in both tabs of postman.
This shows the working tab in postman
This shows the failed tab in postman
My first thought would be that the orange dots in the tabs at the top are indicating that you haven't saved your changes.
One of your requests goes to localhost:5000 and one goes to localhost:3000, is that intentional? You are sending the same data to two different services, so it's possible that the response is different.
I am new to learning about web security. Recentlty, I found a website which has a search bar and the search bar sends a GraphQL query for each input change. If it does not find something, it will return with the exact search query and display 'No results found ...", where '...' is the search query.
If I put the search with a script tag that alerts something and some other specific words, it will return the query and run it on the browser and the alert shows. The thing is, I am not really sure how GraphQL works. The URL of the webpage does not change. I can also see that a GraphQL query was made and it returned the search query (through Chrome Dev Tools Network tab).
Would this specific situation be considered an XSS vulnerability?
I have made a query flow in dialogflow and it has four intent and in the last intent it uses a webhook to get data from server side and displays the result. It is trained automatically and works perfectly in dialogflow console returning response and query answer. The issue is it does not work when I use embedded url. It fails to recognize the name intent and asks (Can you repeat again or fallback intent). I've removed all intents and made query again, there is no similar name intents. Yet it works well in console and not in embedded url.
For the webhook part I've used node.js service.
Please help in this issue.
By 'embedded url' if you mean Dialogflow Web Demo (DWD), you should keep in mind that DWD can be used only for simple text messages. It does not support messages from webhook or even rich responses. However, if you steel need a web widget to embed your bot to your webpage you either create your own or you should use third party solutions (like Kommunicate). Here's the link regarding the limitations of DWD.
I am trying to hit the register API of Pump.io through postman (/main/register), But I am Unable to register, It's showing missing required parameters(Status code 400). Which all parameters or any other thing it requires other than a nickname, password, repeat, and email?
I'm not familiar with pump.io API, but the easiest way to get the request to work in Postman is to open your developer tools in Chrome, go to the network tab, execute the request. Then right click the request and Copy as cURL.
Now go to Postman, hit the Import button, select the 'Paste raw text' tab and paste in the curl command. This gives you exactly the request as executed by Chrome and allows you to change any aspect of it.
This has been driving me nuts all day:
I have an iOS app with a custom URL scheme defined, and am trying to share a link on FB which points to a page that has this scheme in its applink meta tags, so that tapping it should fire up my app.
Every little piece of it is working just fine. I can enter my URL scheme in safari on the phone and the browser launches my app. I have tested my webpage with the FB debug tool and there are no errors or warnings - it correctly identifies all the meta tags.
If I share the link using FB on the phone or on my laptop, all works fine.
HOWEVER, if I share the exact same link using FBSDKShareDialog, it does not work. It just opens the web page with the meta tags as if it was any regular web page.
Anyone has any idea why these two ways of sharing would be different? They look exactly the same otherwise.
If anyone else runs into this problem, here's the reply from FB:
When you share with mode automatic, the app does a fast app switch over to the FB app to show the native share dialog
The post is cached locally on the device, and it does not know about app links (since only Facebook server side knows about it)
When the user opens the FB, the user sees their cached story (with no app links behavior),
This doesn't manifest with the Web mode since the Facebook app needs
to pull from the server to get the post, in which case it has all the
app links info.
This is unlikely something that we'll fix. However, after a while, the
cache will expire, and Facebook app will re-pull the posts from the
servers, in which case the app link data will be available.
In order to test this, you can share the post on one device, and then
try clicking on the post from another device. The app links should
work at that point.
Which is kind of a lame response IMO - they parse the target page to build the preview, how hard would it be to remember the applink and use it?
There could be two possible issues:
Either the one told by #NJ, i.e. you are just trying to open the link in Facebook app, using the same device from which you posted the link.'
Solution - either open link in other device or cose and re-open your facebook app and do multiple refresh
Or You have some error in your meta tags. There is one important thing though, that Facebook never mentions, i.e. they cache the URL you provide.
So any one used the web link with meta tags the first time in Facebook, Whole meta tags will be cached, and you updated meta tags won't be parsed by facebook.
Solution
To get over with the issue, use below link
Facebook debug tool
Input your meta data included web page URL and
-click on show existing scrape information to find any error
Click on Fetch new scrape information for refreshing your URL on facebook. it will clear the cache for that URL in facebook server.