如果0.5x等于0,25那么x减0,08等于多少
如果0.5x等于0,25那么x减0,08等于多少?0.5x = 0.25x = 0.5x - 0.08 = 0.42
为您推荐：
扫描下载二维码java - Set user-agent property in https connection header - Stack Overflow
to customize your list.
Announcing Stack Overflow Documentation
We started with Q&A. Technical documentation is next, and we need your help.
Whether you're a beginner or an experienced developer, you can contribute.
I am unable to properly set the user-agent property for an https connection. From what I've gathered, http-header properties can be set through either the -Dhttp.agent VM option or through . However, setting the user-agent through the VM option causes " Java/[version]" to be appended to whatever the value of http.agent is. At the same time setRequestProperty() only works for http connections, not https (at least when I tried it).
java.net.URL url = new java.net.URL( "" );
java.net.URLConnection conn = url.openConnection();
conn.setRequestProperty("User-Agent","Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0");
conn.connect();
java.io.BufferedReader serverResponse = new java.io.BufferedReader(new java.io.InputStreamReader(conn.getInputStream()));
System.out.println(serverResponse.readLine());
serverResponse.close();
I've found/verified the problem by inspecting http communictions using WireShark. Is there any way around this?
Update: Addition Info
It seems that I didn't look deep enough into the communication. The code is running from behind a proxy so the communication observed is against the proxy, set through -Dhttps.proxyHost, and not the target website (). Anyway, during an https connection, the method is CONNECT, not GET. Here is a wireshark capture of https communication attempt. Like I mentioned above, the user-agent is set through -Dhttp.agent because URLConnection.setRequestProperty() has no effect (user-agent = Java/1.7.0). In this case, notice the appended Java/1.7.0. The question remains the same, why is this happening and how do I get around it?
CONNECT :443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0 Java/1.7.0
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Proxy-Connection: keep-alive
HTTP/1.1 403 Forbidden
X-Bst-Request-Id: MWPwwh:m7d:39175
X-Bst-Info: ch=req,t=,h=14g,p=_156,f=PEFilter,r=PEBlockCatchAllRule,c=1905,v=7.8.
Content-Type: text/ charset=utf-8
Pragma: No-cache
Content-Language: en
Cache-Control: No-cache
Content-Length: 2491
By the way, the request is forbidden because the proxy filters user-agent, the Java/1.7.0 is causing the rejection. I've appended Java/1.7.0 to the user-agent of an http connection and the proxy refuses connection too. I hope i'm not going crazy :).
2,24911025
I've found/verified the problem by inspecting http communictions using WireShark. Is there any way around this
This is not possible. Communication over an SSL socket is completely obscured from casual observation by the encryption protocol. Using packet capture software you will be able to view the initiation of the SSL connection and the exchange of encrypted packets, but the content of those packets can only be extracted at the other end of the connection (the server). If this were not the case then the HTTPS protocol as a whole would be broken, as the whole point of it is to secure HTTP communications from man-in-the-middle type attacks (where in this case the MITM is the packet sniffer).
Example Capture of an HTTPS request (partial):
.n....E... .........../..5..3..9..2..8..
..............@........................Ql.{...b....OsR..!.4.$.T...-.-.T....Q...M..Ql.{...LM..L...um.M...........s. ...n...p^0}..I..G4.HK.n......8Y...............E...A..>...0...0.........
).s.......0
.....0F1.0...U....US1.0...U.
Google Inc1"0 ..U....Google Internet Authority0..
Z0h1.0...U....US1.0...U...
California1.0...U...
Mountain View1.0...U.
Google Inc1.0...U....0..0
Theoretically, the only way to know if your User-Agent header is actually being excluded is if you have access to the Google servers, but in actuality there is nothing in either the HTTPS specification or Java's implementation of it that excludes headers that would normally have been sent over HTTP.
Example Capture of HTTP request:
GET / HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0
Accept: text/html, image/gif, image/jpeg, *; q=.2, /; q=.2
Connection: keep-alive
Both example captures were generated with the exact same code:
URL url = new URL(target);
URLConnection conn = url.openConnection();
conn.setRequestProperty("User-Agent",
"Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0");
conn.connect();
BufferedReader serverResponse = new BufferedReader(
new InputStreamReader(conn.getInputStream()));
System.out.println(serverResponse.readLine());
serverResponse.close();
Except that for HTTPS the target was "", and for HTTP it was "".
Based off your updated question, using the -Dhttp.agent property does indeed append 'Java/version' to the user agent header, as described by the :
http.agent (default: “Java/&version&”)
Defines the string sent in the User-Agent request header in http requests. Note that the string “Java/&version&” will be appended to the one provided in the property (e.g. if -Dhttp.agent=”foobar” is used, the User-Agent header will contain “foobar Java/1.5.0” if the version of the VM is 1.5.0). This property is checked only once at startup.
The 'offending' code is in a static block initializer of sun.net.www.protocol.http.HttpURLConnection:
String agent = java.security.AccessController
.doPrivileged(new sun.security.action.GetPropertyAction(
"http.agent"));
if (agent == null) {
agent = "Java/" +
agent = agent + " Java/" +
userAgent =
An obscene way around this 'problem' is this snippet of code, which I 1000% recommend you not use:
protected void forceAgentHeader(final String header) throws Exception {
final Class&?& clazz = Class
.forName("sun.net.www.protocol.http.HttpURLConnection");
final Field field = clazz.getField("userAgent");
field.setAccessible(true);
Field modifiersField = Field.class.getDeclaredField("modifiers");
modifiersField.setAccessible(true);
modifiersField.setInt(field, field.getModifiers() & ~Modifier.FINAL);
field.set(null, header);
Using this override with https.proxyHost, https.proxyPort and http.agent set gives the desired result:
CONNECT :443 HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0
Accept: text/html, image/gif, image/jpeg, *; q=.2, /; q=.2
Proxy-Connection: keep-alive
But yea, don't do that. Its much safer to just use :
final DefaultHttpClient client = new DefaultHttpClient();
HttpHost proxy = new HttpHost("127.0.0.1", 8888, "http");
HttpHost target = new HttpHost("", 443, "https");
client.getParams().setParameter(ConnRoutePNames.DEFAULT_PROXY, proxy);
HttpProtocolParams
.setUserAgent(client.getParams(),
"Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0");
final HttpGet get = new HttpGet("/");
HttpResponse response = client.execute(target, get);
54.8k7101136
I've found/verified the problem by inspecting http communictions using WireShark. Is there any way around this?
There is no problem here. The User-Agent header is set whether the request is transported via HTTP / HTTPS. Even setting it to something unreasonable like blah blah works on HTTPS. The headers shown below were captured when the underlying protocol used was HTTPS.
Request headers sent via HTTPS
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
User-Agent: blah blah
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Here's the code that triggers the request.
// localhost:52999 is a reverse proxy to xxx:443
java.net.URL url = new java.net.URL( "https://localhost:52999/" );
java.net.URLConnection conn = url.openConnection();
conn.setRequestProperty("User-Agent","Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/ Firefox/19.0");
conn.connect();
java.io.BufferedReader serverResponse = new java.io.BufferedReader(new java.io.InputStreamReader(conn.getInputStream()));
System.out.println(serverResponse.readLine());
serverResponse.close();
Normally, HTTPS requests cannot be sniffed (like @Perception mentioned). Piping the request through a proxy that replaces the root CA with its own fake CA will allow you to see the traffic. A simpler method is to just look at the access log of the target server. But as you can see from the HTTPS request snippet above, the User-Agent header that is sent is correct.
7,99511740
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you're looking for?
Browse other questions tagged
Stack Overflow works best with JavaScript enabledX除以0.5等于6
笑嘻嘻啊0205
x÷0.5=6x=6 x 0.5 =3
为您推荐：
其他类似问题
x/0.5=6x=6 x 0.5 =3
X除以0.5等于6x=0.5×6x=3
X除以0.5等于6x=12
问题应该是求x吧x=3
扫描下载二维码(2x+1)除以0.3=(x+11)除以0.5-0.2 的解是多少?
八嘎少女3n
约等于15.49
为您推荐：
其他类似问题
你这个是不写错了，数太繁琐了
扫描下载二维码5.4X除以0.4等于0.5除以3/5,x是多少?
么和我解释
27X/5:2/5=1/2:3/5 27X/5*3/5=2/5*1/281X/25=1/5X=1/5*25/81X=5/81
为您推荐：
其他类似问题
5.4x/0.4=0.5/(3/5)两边乘0.4*(3/5)5.4x*(3/5)=0.5*0.44.8x=0.2x=0.2/4.8所以x=1/24
5.4x/0.4=0.5/(3/5) 两边同乘0.24(0.4*3/5)，得 5.4x*0.6=0.5*0.4 4.8x=0.2 x=0.2/4.8x=1/24 所以x是1/24
晕只小的上网5.4X/0.4=0.5*5/35.4X/0.4=2.5/31.8X/0.4=2.59X/2=2.5X=5/9
5.4x/0.4=0.5/0.6所以 5.4x*0.6=0.5*0.4所以 x=(0.5*0.4)/(5.4*0.6)
把以上文字写成式子为 5.4x/0.4=0.5/(3/5) 两边同乘0.24(0.4*3/5)，得 5.4x*0.6=0.5*0.4 4.8x=0.2 x=0.2/4.8 x=1/24 所以x是1/24
5.4x/0.4=0.5/(3/5)5.4x/0.4=（0.5*5）/33*5.4x=0.4*0.5*516.2x=1x=5/81
5.4x/0.4=0.5*5/354x=0.5*5*4/354x=10/3x=10/(3*54)x=5/81
扫描下载二维码