Google hack -- inurl:? doesn't work? - search

I want to search some URL within my company's web site, and with at least one "get" parameter.
Something like http://www.mysite.com/info.php?id=212
So, there should be a ? symbol in it.
However, I tried to use
site:.mysite.com filetype:php inurl:?
And got so many pages without any GET parameter, why does the inurl:? not work?

As you can see here http://support.google.com/websearch/bin/answer.py?hl=en&answer=2466433:
Generally, most punctuation and special characters are ignored in Google Search.
That includes the question mark, and that's why your search doesn't work.

Related

Custom query string in domino URL

Need a way to pass a value between to pages using URL query strings if possible. However everytime I add "?customquery=customvalue" at the end it ends up to the 404 page of the website.
I want to basically make it look like this.
https://example.com/somedepartment/sample.nsf/page/hello+world?customquery=customvalue
hello+world is a document that is equivalent to a webpage.
I tried this plus a javascript that collects the strings after the number sign and it works.
https://example.com/somedepartment/sample.nsf/page/hello+world#customvalue
However, I couldn't use the hash sign because they told me not to use it and use another unique symbol instead. I am not aware of any symbols that could work the same with hash sign. If there is, please enlighten me.
Apparently, I was able to find an answer.
https://example.com/somedepartment/sample.nsf/page/hello+world?OpenDocument&RandomParam=sample
Now I could pass values by means of this format. Basically it has to be preceded by "OpenDocument" parameter before putting custom ones.
This documentation also helps: http://www.ibm.com/developerworks/lotus/library/ls-Domino_URL_cheat_sheet/

Exact match in google search

I am trying to make an application which find all the copied code in a project.
But basically my question is purely related to google search.
I made a search for the keyword "public void bubbleSort(int[] arr){"
and this was the result.
In the first page of search results, only the last url makes a perfect match with my keyword.
Can i tell google with some search keywords so that it will give more importance to pages with an exact match of my search keyword?
although the plus sign, +, is no longer an available Google search filter, you can use quotes, or after running the query selecting Search Tools and then verbatim under the All Results drop down.
You can also search the Google code archives, https://code.google.com/ or try some of the other code search engines around the Internet.
+"public void bubbleSort(int[] arr){"
the plus sign means to include this term no matter what. the quotes turn the loosely coupled words into a single term.
for a full list of Google syntax operators:
[web]: https://support.google.com/websearch/answer/136861?hl=en

Do I need to build a web form to use this web call?

When I replace the two options in this web call directly in the URL, I don't get the expected results.
https://secure.trademark-clearinghouse.com/tmch/public/labels?name=a%26b&jurisdiction=BX
Do I need to build a web form to use this web call?
Or am I replacing the options incorrectly?
Thanks.
Apparently you are using URL parameters to send some information
name=a%26b&jurisdiction=BX
means:
parameterName=parameterValue separed by "&" symbol.
in your case:
name="aɫb"
jurisdiction="BX"
If you want to just read that, will work without a form.
Any further explanation we will need more information about what do you want to do. But this symbol between the "a" and "b" is strange. As you can see here http://www.nicolas-hoffmann.net/utilitaires/codes-hexas-ascii-unicode-utf8-caracteres-usuels.php the code %26b is "ɫ" if you really want this in your data... it's okay.

How can I make clean search urls?

If I have search that has a lot of different options, then url becomes very long and looks very bad. Is there anyway to make urls look better? Using POST to make search would keep urls clean, but people couldn't share search urls.
Try doing an advanced search with many options on Google: the URL is long and not especially human-readable. I really don't think that's a problem; I don't think many people read URLs often. If you expect people to share search results, then show a button on the search results page that will generate a tinyURL-style shortened URL for that particular query.
A POST is meant for something that changes server state (e.g. a database update) and really shouldn't be used for a search.
You can encode all of your search criteria into something like a hash and then have a single parameter in your querystring that has that value:
http://www.mysearch.com/query=2esd32d2csg3fasfdlkjSDDFdskjsEWFsDFFR39fdf
I'm not sure exactly how you'd encode everything, but it wouldn't be too difficult.
Do the different options actually need to be in the URL? For example, a quick search from my Firefox search window gives a URL like:
http://www.google.com/search?q=search&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a
If I'm sending the link to anyone, I habitually cut off everything after q=search. Why not have the URL be the bare minimum that you need to send the link to someone (or bookmark), and make the rest as invisible POST variables?

Sharepoint Navigation URL in All Capital Letters

I see this behavior from time to time where a site's URL will be in all capital letters when linked from the navigation. The site's name is not all caps, and the URL is properly cased in most situations. The all uppercase treatment appears to come and go, and is not related to anything. Has anyone else seen it or know how to stop it from happening?
I've just looked into this myself. It's part of the internal caching; sharepoint converts part of the links to uppercase to make the comparison case insensitive. As far as I can tell there's nothing you can do about it.
http://support.microsoft.com/kb/953457
Check the welcome page setting for the site - that's where the link used in navigation comes from.
I have seen it... my development team caused it when they created a custom navigation provider and needed to check values in the URL. They converted the URL to all uppercase to make the string finds easier.

Resources