Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected response(403 Forbidden), to the authorization request. Missing header:[Location]! #1505
Unexpected response(403 Forbidden), to the authorization request. Missing header:[Location]! #1505
Comments
With OCP 4.0 / 4.1 (Kubernetes Master Version v1.13.4+81fc896) we are facing problem with fabric8 client authenticating using username/password — IOException: Unexpected response(403 Forbidden), to the authorization request. Missing header:[Location]! We have workarounded it by using token. Same code works ok with OCP 3.11
Caused by: java.io.IOException: Unexpected response(403 Forbidden), to the authorization request. Missing header:[Location]! at io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.authorize(OpenShiftOAuthInterceptor.java:133) at io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.acquireNewToken(OpenShiftOAuthInterceptor.java:111) at io.fabric8.openshift.client.internal.OpenShiftOAuthInterceptor.intercept(OpenShiftOAuthInterceptor.java:63) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200) at okhttp3.RealCall.execute(RealCall.java:77) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:379) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:344) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:313) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:296) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleGet(BaseOperation.java:826) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.getMandatory(BaseOperation.java:243) . 47 more The text was updated successfully, but these errors were encountered:
java.io.IOException: Server returned HTTP response code: 403 for URL
Add the code below in between uc.connect(); and uc.getInputStream(); :
uc = url.openConnection(); uc.addRequestProperty("User-Agent", "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)"); However, it a nice idea to just allow certain types of user agents. This will keep your website safe and bandwidth usage low.
Some possible bad ‘User Agents’ you might want to block from your server depending if you don’t want people leeching your content and bandwidth. But, user agent can be spoofed as you can see in my example above.
Solution 2
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
You need to contact the owner of the site to make sure the permissions are set properly.
EDIT I see your problem. I ran the URL through Fiddler. I noticed that I am getting a 407 which means below. This should help you go in the right direction.
10.4.8 407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in «HTTP Authentication: Basic and Digest Access Authentication»
Also see this relevant question.
Solution 3
IF the browser can access the page, and your code cannot, then there’s something different between the browser request and your request. You can look at the browser request, using, say, Firebug, to see what the differences are. Some things I can think of are:
- The site sets a cookie (maybe during login). You may be able to handle this in code, you will have to explicitly add support for passing the cookie. This is most likely.
- The site filters based on user agents. You can set the user agent. This is not as likely.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While Synch the a/c it is giving «HTTP Error (java.io.IOException): 403 : Forbidden» #12
While Synch the a/c it is giving «HTTP Error (java.io.IOException): 403 : Forbidden» #12
Comments
While Synchronizing users a/c it is giving «HTTP Error (java.io.IOException): 403 : Forbidden»
Here is log
`[ERROR] : TiHTTPClient: (TiHttpClient-2) [19368,19368] HTTP Error (java.io.IOException): 403 : Forbidden
The text was updated successfully, but these errors were encountered: