Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I'm using Fiddler to setup a proxy server, but when enabling "Require Proxy Authorization" under the rules menu the username/password is always 1. How do I change the username/password?
I tried changing oSession["X-AutoAuth"] = "username:password"; but it doesn't change the proxy credentials required.
Can't find anything in the documentation regarding this...
The X-AutoAuth flag concerns what credentials Fiddler sends to an upstream server when automatically replying to an authentication challenge; it has no impact on what credentials are demanded of the user.
This question was original asked and answered here: https://groups.google.com/forum/#!topic/httpfiddler/pErxaOtMlyc
You can change the credentials expected by Fiddler by setting the preference fiddler.proxy.creds to the base64 encoded username:password string. The default value is MToX which is the base64 encoded version of the string 1:1. You can compute the base64 value you need using the Tools > TextWizard feature in Fiddler.
To update the preference, click into the QuickExec box below Fiddler's Web Sessions list and type prefs set fiddler.proxy.creds YOURBASE64StringHere and hit Enter.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I want to disable external access to ECP Exchange 2016. How to do it?
I will read main step for solution.
Run the Add Roles and Features Wizard from the Exchange Server. Select your Exchange Server and follow the wizard. Now you are on the Server Roles tab. Expand Web Server (IIS) -> Web Server -> Security. Check the IP and Domain Restrictions role. On our end, it’s already installed on the Exchange Server.
Click on Next. Click Install to install the IP and Domain Restrictions role. Installation completes. Proceed further with the steps below.
Open IIS Manager on the Exchange Server. Expand Server -> Sites -> Default Web Site. Select ecp. Double click on IP Address and Domain Restrictions.
The IP Address and Domain Restrictions feature is open. Let’s configure it to disable external access to ECP on the Exchange Server 2016. First, click on Edit Feature Settings… and configure it to Deny access for unspecified clients. Set the Deny Action Type to Not Found.
Click on Add Allow Entry… and configure that you can access ECP internal on the Exchange Server (localhost). Add the IP 127.0.0.0 with prefix 8. If you want to add the subnet mask instead of the prefix, it should be 255.0.0.0.
You added the entry. Now you can log in ECP from the Exchange Server, go to https://localhost/ecp. I don’t recommend to open ECP on the whole internal LAN. If you have management servers, add the IP addresses to the allow list.
You added the entries and it is showing correctly. Start ECP and login from the IP addresses that you added. Make sure you insert the Exchange Server hostname. For example, https://EX01/ecp.
Source: https://www.alitajran.com/disable-external-access-to-ecp-exchange-2016
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I'm developing a web application for use inside our internal Windows domain. I have 3 servers: apps.mycompany.com (primary), api.mycompany.com, and files.mycompany.com. Right now, everything works fine over HTTP. But I need to have these accessible over SSL/https to Windows desktop clients on the network (Chrome/Firefox/Edge) and iOS (Safari/Chrome).
I've set up self-signed certs using OpenSSL, and have configured nginx to where they respond correctly, and serve data. But, I'm constantly running into "not secure" / "invalid certificate" errors and "mixed content" (http/s) warnings that stymie my development. The errors on api and files are especially pernicious, as they just "break" things not obvious to the user.
I need a solution where everyone can simply hit https://apps.mycompany.com... and everything "just works", without user intervention (allowing insecure connections, manually adding certs, adding certificates to Trust stores, etc.)
Advice?
EDIT: I see this question was closed. Isn't setting up SSL/https an integral part of modern web development? (and yes, I had already asked my question on Server Fault).
You need to create a root certificate that would be trusted by all your clients. Then you can sign server certificates with that "root" key so that server certificates would also be trusted.
This is the example how you can issue such certs.
More challenging task is to install this root cert to all your clients. You can ask your domain administrator to help you with that. Otherwise you will have to ask all your users to install that root cert (they will also probably have to be local administrators..)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Actually, today morning purchased my new domain in Bigrock. I dont know what to do here after. I want to upload my files to my registered domain. But how can i do this?
I'm trying to connect via filezilla to upload content of registered domain.. but getting this error
Status: Resolving address of domainname.com
Status: Connection attempt failed with "EAI_NODATA - No address associated with nodename".
also tried ftp.domainname.com
Status: Resolving address of ftp.domainame.com
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
What will i have to do now?
Question 1 : First step what to do?
Question 2 : what is user name and password have to give in filezilla to upload contents. Whether it is site password or acc password?
Before you get any further, ask yourself this question. did you setup a FTP user and/or hosting? Sounds like you haven't.
If not, that is step 1. You need to get hosting setup first, during that process you should be able to use your user and pass that was setup for FTP login.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a website hosted in my dedicated server. When I am now trying to access my website(in firefox) its saying This Connection is Untrusted .
Do I need to change something in my source code or I should ask hosting company about it ?
You are trying to access a secure (https) site without a valid certificate. You need to get a valid certificate (chat to your hosting company about that) or not use HTTPS.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am trying to get the Candy.js example to connect to a locally installed ejabberd server that I have configured according to this tutorial.
I know nginx is proxying correctly because I can navigate to the URL I specified in the nginx configuration file and the ejabberd HTTP binding placeholder page will display correctly.
I can also connect and log into to the ejabberd server normally through an XMPP client like Pidgin. Pidgin will also connect over BOSH perfectly fine when I specify the BOSH URL in the account setup.
When I login with Candy.js with debugging turned on, it tells me it has actually logged in successfully. It then returns a 504 error. I can also look at the ejabberd "online users" page and it will confirm that I am logged in.
So my question is, what am I doing wrong and how can I get the Candy.js example page working correctly?