I need to request the following URL:
http://myhost.com/api/v3/projects/digitalis%2Fbackend/issues
but this URL is being sent:
http://myhost.com/api/v3/projects/digitalis%252Fbackend/issues
Go to the Preferences (Paw menu), tab "HTTP" and uncheck "Re-encode Percent Escapes". It should be working fine.
Related
I have a question.
Does setting a post/page staus to "private" will it generate a true 404 page with 404 header? Or it's just a page showing that is not found?
I want Google to know that the page no longer exists and it's 404.
Settings to private makes the site say it's not found, but how do I know it's a true 404 error?
Thanks! :)
What you are looking for is the HTTP response status of the URL.
You have to look about. Google about something like "get HTTP status of a URL", and you'll find many free tools to check URLs HTTP statuses.
You can also check yourself with your browser console whether it's a real 404 or not.
In the network tab, you'll have the page request lists and HTTP status for each. From there, check the request having your page URL (usually the first one), and see the HTTP status of this request. If it's a 404: you're good.
You can also use Postman to get the HTTP response status of your URL. Or on CLI using Curl and many other ways.
When I try to use Facebook login on this site:
https://parlay.io
by clicking the button at the top of the page, I get a popup with the URL:
https://www.facebook.com/login.php?skip_api_login=1&api_key=501604519940587&signed_next=1&next=https://www.facebook.com/v2.2/dialog/oauth?redirect_uri=https%3A%2F%2Fparlay.io%2F_oauth%2Ffacebook%3Fclose&display=popup&state=eyJsb2dpblN0eWxlIjoicG9wdXAiLCJjcmVkZW50aWFsVG9rZW4iOiJxd01acHRSb3hGX0hDM1FEV25vSVVSVXlDZTZWcWVFNUhrUHZVcHA5ZWhUIiwiaXNDb3Jkb3ZhIjpmYWxzZX0%3D&scope=email%2Cuser_friends&client_id=501604519940587&ret=login&cancel_url=https://parlay.io/_oauth/facebook?close&error=access_denied&error_code=200&error_description=Permissions+error&error_reason=user_denied&state=eyJsb2dpblN0eWxlIjoicG9wdXAiLCJjcmVkZW50aWFsVG9rZW4iOiJxd01acHRSb3hGX0hDM1FEV25vSVVSVXlDZTZWcWVFNUhrUHZVcHA5ZWhUIiwiaXNDb3Jkb3ZhIjpmYWxzZX0%3D#=&display=popup
I enter in my Facebook creds and submit. In Safari, this works and login completes. In Chrome, the popup goes blank but stays open. The popup URL is
https://parlay.io/_oauth/facebook?close&code=...
The popup console says:
Uncaught SecurityError: Blocked a frame with origin "https://parlay.io" from accessing a frame with origin "http://parlay.io". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match.
The error occurs on line 23:
I don't know why this popup is trying to access http://parlay.io. I do not have http or http://parlay.io as a setting anywhere in my app.
This is using the 'popup' style oauth. When I switch to 'redirect' style in Chrome, the first time I login, I get this error on the server:
{"line":"398","file":"oauth_server.js","message":"Error in OAuth Server: redirectUrl (http://parlay.io/) is not on the same host as the app (https://parlay.io/)","time":{"$date":1435164688847},"level":"warn"}[parlay.io]
and I get redirected to same signin page. The second time I click login, it works. The second click can be automated with:
I had the exact same problem, under similar conditions (Meteor 1.3.x, ROOT_URL set to https, FB/Twitter apps set to https.)
What fixed the problem for me was to set up my site to always redirect HTTP requests to HTTPS. I am using Cloudflare, so I followed the instructions here:
https://support.cloudflare.com/hc/en-us/articles/200170536-How-do-I-redirect-all-visitors-to-HTTPS-SSL-
After making the change, sign-in worked like a charm across different machines. Final results here:
https://goodbyegunstocks.com
Why would a site respond with an HTTP 302 (redirect) and include HTML in the payload. Check out godaddy.com. You will need an account to log in. When you log in you will see in an HTTP trace (I use firebug), a 302 returned with the location: header as expected, however the payload includes the complete HTML page. Next, as expected, you see the URL from the location header fetched with the same HTML payload. Why would they do that?
I don't know anythign about GoDaddy but it may be a way to somewhat post information back to their server but not force your browser to do an "auto form post". I'm working with ADFS currently and with that security (and many others) the authentication authority sends back a 200 with html of a form, which when loaded immediately posts that form to your server.
I'm currently experimenting with sending back a 302 with the payload that redirects back to the server instead. This prevents a flash of white as that auto-post is taking place.
It's just a guess :)
I have old asp classic project, which has redirect rule in web.config, so when user comes from old browsers he is redirected to some page. But in this page should be a button like "No, i want to use old browser", that should redirect person to page he was previously.
QUESTION
Is it possible to know the previous URL when there is redirect and no link to that page (HTTP_Referrer isn't working).
Thanks for your attention!
You can try using javascript:
Back
Or
window.history.back()
You can request the HTTP host:
Request.ServerVariables("HTTP_HOST")
The browsers user agent isn't required to set the HTTP_REFERRER but host header has been required since HTTP 1.1.
I am creating a searching website using ASP.NET .On my one page I show URL of results.When I click on URL a new link is open but the URL path for the new link in the browser include loalhost:portnumbet.I do not want this in my URL.
For eg.
result
so on clicking result I go to browser where the URL is "https://localhost:8080//www.google.com"
why this localhost:8080 includes in the URL.
Thanks
When you are redirecting to the URL, you will not be adding any protocol information, so it will default to the current website/protocol.
For example;
Response.Redirect("www.google.com")
is not the same as;
Response.Redirect("http://www.google.com")
You need to add the fully qualified URL, otherwise it will believe it to berelative to the current website, therefore add the http(s):// to the redirect.