I know this is a question that many of you will think that can be solved easily by pushing using https, but I cannot push over https.
I have a repository that I need pushed into Bitbucket, however, the way they allow to push is on https, which is obviously a good idea, but I cannot use https, so, does anybody knows if there is a way to push a repository into Bitbucket using http? I know that this has many security issues, but I have to deal with the fact that the ssl port is closed on the proxy I'm behind.
Ideas?
Unfortunately not - are you able to use SSH instead?
From the BitBucket documentation: "You can use either secure hypertext transport protocol (HTTPS) or secure shell (SSH) to connect to bitbucket."
For anyone reading this, we encountered this issue today (proxy denied https). We tried using http instead of https for Bitbucket, and it just worked.
Related
I'd like to implement kind of SSO for openshift, what I mean: from my webapp a user can open openshift console in a new window without giving his credentials. I've configured Basic Authentication Remote and it's working, can open new window and post username/password but it's looks that openshift is protected with crsf token. Thus not sure if it's possible at all. It seems that developing custom identity provider is not supported either. Any idea ?
PS I'm aware of Request Header Identity Provider but that solution requires my webapp to provide idp functionality (not even sure if it's feasible), also apache (we use nginx), a lot of issues for dev to install it all on a single computer due to port conflicts, valid ssl etc etc
Best option will be to use oauth proxy. See if this helps in your case.
https://github.com/openshift/oauth-proxy
Finally I've implemented SSO using js postMessage to send user/token data and Basic Authentication Remote.
Is it possible to forward locally-server site (but served with https) via remote debugging somehow?
My site is served via https because it uses some also https-based API. But it seems like there is no option now to forward it straightly.
It seems to work. If you forward port 1234 to localhost:8080, then you should be able to access https://localhost:1234 on your device.
There's no spot to specify a protocol because it's a straight port forward.
I need to access a IP restricted website. Since the IPs of my coworkers any my own one changes all the time I would like to use one of my root servers running Nginx as a Proxy in Chrome and Firefox.
Yet I don't know how to set up Nginx for that kind of usage. Googling is also difficult because the term proxy is used in a lot of different contexts.
Can I configure Nginx to act as a HTTP proxy to that page, if yes, how do I set it up?
Note: I can't use it as a reverse proxy to the page. It does work but all links on the page point to the original URL which I can't fix easily (at least I don't know how).
Is there any reason why a file may load over http but not over https?
I am curious because I just enabled ssl on a subdomain and it does not seem to be properly. I can see the green lock but if i load the site with it, i see no files.
Like if I have a file at
http://site.exmpl.org/file.html
when i go to
https://site.exmpl.org/file.html
it does not load.
I have ssl enabled because i have the green lock, also i am using cloudflare if that helps
I assume that you may have your SSL mode configured to "Full" in the CloudFlare Crypto section- But lack a ssl certificate installation on your subdomain.
--If not--
You may not have SNI or a Dedicated IP setup for your website then your apache server is likely using your certificate, but connecting to the web space of whoever first setup a SSL Certificate on that server. This is often a problem on shared web hosting environment. You can attempt to contact your provider to ask for help in getting SNI properly configured. You can also acquire a Dedicated IP from your provider.
in cloudflare dashboard under SSL/TLS section go to Edge Certificate instead of overview.
In Edge Certificate there is option called "Always Use HTTPS" which explains "Redirect all requests with scheme “http” to “https”. This applies to all http requests to the zone." just turn in on and after sometimes you are good to go.
I've configured hgweb.cgi behind iis7 on windows server 2008. I can pull the repository just fine. However whenever I push I get a 502 bad gateway. I've found a posting which seems to indicate this is a problem with the mercurial config on the server. mercurial doesnt seem to be picking up an http proxy (fiddler) from my local machine even if its configured.
Questions are:
how do I 'fix' the 502 problem?
failing that how do I make mercurial use the proxy so I can figure out whats going wrong?
how do I adjust the verbosity setting for mercurial 'properly' given that this is running under a webserver?
It sounds like this problem.
I was having the same issues with pushing a repository, but it went away after I had installed a later version of Mercurial (2.0.1). I used the instructions here, (paying attention to the comment to that post by Ethan J Brown).