IE 6.0 seems not compatible with iplanet web proxy server 3.6

We have Iplanet Web Proxy Server V3.6 on AIX 4.3.3, and is trying to roll out IE browser V6.0. And is experience following problem:
When first try to access an ACL controlled URL, after enter user name and passwed, it would say "page cannot be found", and user has to click on "Refresh" botton, then it is OK. Subsequent access are all fine.
It seems to be a bug to me with proxy server. Currently, there are only SP2 for V3.6 available on the download site. However, from the release notes, it does not say it is fixing this specific problem.
Anyone can advise on this ?

I think this one is fixed in SP3. Can you try to upgrade and see if the problem still persists.

Similar Messages

HT5364 Why is safari not compatible with some web sites

Why is safari not compatible with some web sites

Web site design. Information.
https://discussions.apple.com/message/11615727#11615727
https://discussions.apple.com/message/21612250#21612250

Oracle iPlanet Web Proxy Server 4.0.14 not getting started.

bash-3.00# ./start
ld.so.1: parsexml: fatal: relocation error: file parsexml: symbol __RTTI__1nMXMLException_: referenced symbol not found
ld.so.1: parsexml: fatal: relocation error: file parsexml: symbol __RTTI__1nMXMLException_: referenced symbol not found
ld.so.1: parsexml: fatal: relocation error: file parsexml: symbol __RTTI__1nMXMLException_: referenced symbol not found
ld.so.1: parsexml: fatal: relocation error: file parsexml: symbol __RTTI__1nMXMLException_: referenced symbol not found
Oracle iPlanet Proxy Server 4.0.14 B06/08/2010 05:46
failure: CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of /export/home/Oracle_Proxy/bin/proxy/lib/libj2eeplugin.so failed (ld.so.1: proxyd: fatal: libjvm.so: open failed: No such file or directory)
bash-3.00# uname -r
5.10
bash-3.00# uname -a
SunOS sunfire-v240 5.10 Generic_118822-25 sun4u sparc SUNW,Sun-Fire-V240
bash-3.00#
The web proxy server version is 4.0.14 and the package i used is "Oracle-iPlanet-Web-Proxy-Server-4.0.14-sparc.zip"
Please help me. If any other information is needed, please let me know.

Your proxy instance should start. The error you are seeing should only be for the admin server. Add the location of where your jvm.so is located to the LD_LIBRARY_PATH. The jvm.so is located under the JDK directory.

Bug Report: JSSE 1.0.2 & iPlanet-Web-Proxy-Server/3.6

When tunneling through iPlanet-Web-Proxy-Server/3.6 we get a "Socket Closed" exception during the handshake (right after overlaying the tunnel). I got this problem with HP-UX. My browser works fine with that proxy so the problem isn't the proxy. And my code works fine with every other proxies. This proxy does return HTTP 1.0 so this well known issue isn't related.
Anyone from Sun can confirm this issue ?
Anyone else got this bug ?
Thanks in advance.
Fran�ois

Hi all,
When you say tunnelling, are you referring to code similiar to the code in JavaWorld Tip 111?
I am currently trying to debug some issues with that code myself. I get similiar errors when tunnelling through a proxy.
The download works correctly when a HttpsURLConnection is used to connect directly to the same site.
I am using a squid-cache as my test proxy, so I am not sure if the proxy is the problem. (assuming we are talking about the same issue)
I have noticed that a V3 site certificate seems to be more likely to fail though. I have not found a site using a V1 certificate where the tunnelling has failed.
We are also discussing what I think is the same issue in the thread "HTTPS tunneling and V3 certificates".
I have been trying to get this stuff working for a few months now.

Upgrade question (iPlanet Web Proxy Server)

Hello List,
What is the procedure for upgrading iPlanet Web Proxy Server 3.6 (beta)
to iPlanet Web Proxy Server 3.6 on Solaris 2.8?
Thank you in advance.
- Andrew Petrov.

Hi
This as per the HTTP/1.1 RFC (RFC2616)
The Connection general-header field allows the sender to specify options that are desired for that particular connection and MUST NOT be communicated by proxies over further connections.
The Connection header has the following grammar:
Connection = "Connection" ":" 1#(connection-token)
connection-token = token
HTTP/1.1 proxies MUST parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header field(s) from the message with the same name as the connection-token. Connection options are signaled by the presence of a connection-token in the Connection header field, not by any corresponding additional header field(s), since the additional header field may not be sent if there are no parameters associated with that connection option.
Read the following at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.3
and
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10
Regards
Nagendra HK

Migrate certificate 3.x to Oracle iPlanet Web Proxy Server 4.0.20

Hi
I try to migrate from Sun iPlanet Web Proxy Server(SPWPS) 3.6 to Oracle iPlanet Web Proxy Server(OPWPS) 4.0.20 and I have some problem.
I have an instance in SPWPS-3.6 with SSL certificate, when I migrate it to OPWPS-4.0.20 using the admin interface, the certificate
is not migrate with this error message :
Migrating Keys and Certificates...
[Error] The password entered for the key is not valid
Assimilation failed.
But I am sure to enter the right password.
After that I manage the new instance in administration interface, and in Security Panel, there is a choice to "Migrate 3.x certificate"
I try this, but I get this error message
Incorrect Usage
The password entered is not valide
Can somebody help me to resolve this problem ?
Thanks in advance.

Your proxy instance should start. The error you are seeing should only be for the admin server. Add the location of where your jvm.so is located to the LD_LIBRARY_PATH. The jvm.so is located under the JDK directory.

IPlanet Web Proxy Server 3.6 and emptying out the cache.

Hello.
I'm wanting to empty out our proxy server's cache in an attempt to resolve one of our users help desk problems - a web site they are accessing is not loading correctly when going through the proxy server, bypassing the proxy server works.
The problem is that the technician who implemented our iPlanet Web Proxy Server 3.6 has left the company and no one else is aware of how to do this. Can anyone advise of what has to be done to achieve it? Thank you.
Kind regards,
Jimmey.

Hi
This as per the HTTP/1.1 RFC (RFC2616)
The Connection general-header field allows the sender to specify options that are desired for that particular connection and MUST NOT be communicated by proxies over further connections.
The Connection header has the following grammar:
Connection = "Connection" ":" 1#(connection-token)
connection-token = token
HTTP/1.1 proxies MUST parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header field(s) from the message with the same name as the connection-token. Connection options are signaled by the presence of a connection-token in the Connection header field, not by any corresponding additional header field(s), since the additional header field may not be sent if there are no parameters associated with that connection option.
Read the following at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.3
and
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10
Regards
Nagendra HK

IPlanet Web Proxy Server 3.6 SP 5 Persistent Connection doesn't work

I use iPlanet-Web-Proxy-Server/3.6-SP5 on Soloaris. and trying to use persistenet connection functions in forward proxy through setting keep alive to "ON". But I found this functions doesn't work at all. The following trace is the HTTP Header info i got from receiver.
1. The HTTP Header info without using Proxy Server
Request headers :
proxy-authorization: Basic YXBwLWVtcXVzZXI6MTIzNDU2Nzg=
connection: Keep-Alive
proxy-connection: Keep-Alive
server: IBM WebSphere MQ internet pass-thru V1.3.2
accept: application/octet-stream
host: 10.1.13.43:1414
user-agent: 10.1.72.254:1414
content-type: application/octet-stream
content-length: 132
accept-encoding: identity
2. The HTTP Header info using Proxy Server
Request headers :
server: IBM WebSphere MQ internet pass-thru V1.3.2
accept: application/octet-stream
host: 10.1.72.254:1414
user-agent: 10.1.72.254:1414
content-type: application/octet-stream
content-length: 132
accept-encoding: identity
date: Mon, 06 Sep 2004 18:04:12 GMT
forwarded: by http://iaccess.mor.cr:8085 (iPlanet-Web-Proxy-Server/3.6-SP5)
via: 1.1 S1PS,1.1 S1PS
I found Kepp-Alive information ( "connection: Keep-Alive" and " proxy-connection: Keep-Alive")
was taken out by proxy server.
Is a proxy server bug? Can I do something to make it work?
Regards,
songtao

Hi
This as per the HTTP/1.1 RFC (RFC2616)
The Connection general-header field allows the sender to specify options that are desired for that particular connection and MUST NOT be communicated by proxies over further connections.
The Connection header has the following grammar:
Connection = "Connection" ":" 1#(connection-token)
connection-token = token
HTTP/1.1 proxies MUST parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header field(s) from the message with the same name as the connection-token. Connection options are signaled by the presence of a connection-token in the Connection header field, not by any corresponding additional header field(s), since the additional header field may not be sent if there are no parameters associated with that connection option.
Read the following at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.3
and
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10
Regards
Nagendra HK

Is iPlanet Web Proxy Server support OpenLdap authentication ?

Do you know Is iPlanet Web Proxy Server support OpenLdap authentication ?
Thanks
Regards,

Hi
This as per the HTTP/1.1 RFC (RFC2616)
The Connection general-header field allows the sender to specify options that are desired for that particular connection and MUST NOT be communicated by proxies over further connections.
The Connection header has the following grammar:
Connection = "Connection" ":" 1#(connection-token)
connection-token = token
HTTP/1.1 proxies MUST parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header field(s) from the message with the same name as the connection-token. Connection options are signaled by the presence of a connection-token in the Connection header field, not by any corresponding additional header field(s), since the additional header field may not be sent if there are no parameters associated with that connection option.
Read the following at
http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1.3
and
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.10
Regards
Nagendra HK

Safari cannot open the page ~ The error was: "There was a problem communicating with the web proxy server (HTTP)

Help! I was cruzing along just fine and went out tonight only to receive the message above:
Cannot open Page
Safari cannot open the page
The error was: "There was a problem communicating with the web proxy server (HTTP)."
I have had all the Apple iPhone phone. Have never encountered anything like this.
All systems are GO as soon as I log on to wifi.
Can anyone help, please.

I am also fixed. I also loaded Onavo, but that was the other day ... this is what I did with the help of online chat with AT&T ...
I went to:
Settings
Wifi
I selected the network I was working on by hitting the blue arrow located on right side
At the detail page of that network I scolled down to the bottom to find HTTP Proxy boxes
I was on Off and changed it to Auto and it worked!
I was soo jazzed!!
Instructions said if it was already on AUTO, to change it to Manual and make your Port = 80 but I didn't have to do that!
YIPPIE!! I'm a new man!!
Go to settings -----> WI-FI -----> select the network you're using ------> hit the blue arrow located on the right-side of the network name (ie: show details of that network), this takes you to another page.
--------> at the bottom of the page you'll see "HTTP Proxy" boxes (located below the "renew lease" button) ---------------> change the proxy to AUTO. Note: if you're already at AUTO, change it to "Manual" and make your Port = 80.

'-1' bytes in log file - iPlanet Web Proxy Server 3.6

I'm running iPlanet Web Proxy Server 3.6, and getting strange results in log file using extended format. Where the number of bytes should be (c1 - the content-length sent to the client by the proxy).
I regularly get a '-1' instead of the number of bytes. Anyone tell me where this is coming from and how to stop it?

Someone in the Web Proxy Server forum might. I guess you accidentally posted in the Web Server forum. However, if your question is time- or business-critical, you should probably contact Sun directly: http://www.sun.com/support

Iplanet Web Proxy Server 4.0.19 error 400

Getting error 400 after upgrading Iplanet Web Proxy 4.0.19
Message from Iplanet Web Proxy 3.6 - working properly
Iplanet Web Proxy 3.6 SP12
202.123.21.57 - - [26/Apr/2013:20:21:05 +0400] "POST /as1.html HTTP/1.1" 200 58 200 58 12 12 309 52 427 19 0 DIRECT FIN FIN DO-NOT-CACHE
197.226.57.153 - - [26/Apr/2013:20:21:16 +0400] "GET /AA8002.html?^CfSb_AA HTTP/1.1" 200 29 200 29 - - 255 52 370 19 0 DIRECT FIN FIN DO-NOT-CACHE
197.226.57.153 - - [26/Apr/2013:20:21:16 +0400] "GET /AA8003.html?^CfSb_AA HTTP/1.1" 200 0 200 - - - 255 52 370 19 0 DIRECT FIN FIN DO-NOT-CACHE
Message from Iplanet Web Proxy 4.0.19
Iplanet Web Proxy 4.0.19
202.123.21.57 - - [26/Apr/2013:20:24:57 +0400] "POST /as1.html HTTP/1.1" 200 58 200 58 12 12 315 208 562 19 0 DIRECT FIN FIN DO-NOT-CACHE
202.123.21.57 - - [26/Apr/2013:20:24:57 +0400] "-" 400 - - - - - - - - - - - - - -
197.226.57.153 - - [26/Apr/2013:20:25:14 +0400] "-" 400 - - - - - - - - - - - - - -
197.226.57.153 - - [26/Apr/2013:20:25:14 +0400] "-" 400 - - - - - - - - - - - - - -
Any help
Manoven

Your proxy instance should start. The error you are seeing should only be for the admin server. Add the location of where your jvm.so is located to the LD_LIBRARY_PATH. The jvm.so is located under the JDK directory.

SB-Messaging and service bus DLL within BTS seems not compatible with Cloud

I am trying to retreive a message from a Queue in azure service bus. The receive location gets disabled after 5 seconds of enabling it. The error message is :
The receive location "rlFromFireQueue" with URL "sb://muazure.servicebus.windows.net/firealertqueue" is shutting down. Details:"System.InvalidOperationException: This client is not supported for a partitioned entity. The client version
should be greater or equal than version '2013-10'..8653aa96-4c37-4ee1-8be8-52f2e9702ee0_G2_G2 ---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: This client is not supported for a partitioned entity. The client version should
be greater or equal than version '2013-10'..8653aa96-4c37-4ee1-8be8-52f2e9702ee0_G2_G2
I had the same exact issue when I was using an old .Net console application which was using microsft.servicebus.dll version 2.1. I downloaded the 2.4 azure sdk and ran setup. After replacing the reference in my console project to the new version I was able
to send messages to my queue.
My BTS box is 2013 R2 (upgraded from 2013), I checked the directory C:\Program Files (x86)\Microsoft BizTalk Server 2013, I noticed that the Microsoft.ServiceBus.dll in this directory is version 2.1 which according to a thread in blog is not compatible
to a new property introduced since last summer ( clients will be updated to support partitioned entities) when creating a new queue using Quick Create.
So my question is : How can I update the SB-MESSAGING adapter to use a new version to be compatible with this improvments in Azure or more clearly is there any config or procedures to be done to make the bTS 2013R2 adapter compatible with Azure service bus
partioning feature
For your reference, here is the url for the blog where I found the information
http://mindovermessaging.com/2014/06/21/service-bus-queuetopic-partitioning-not-supported-in-biztalk-services/
Thanks in advance

I'm afraid you wont be able to update the SB-Messaging adapter because the partitioning option is not supported.
However you have an alternative:
You can try using a WCF-Custom port with netMessagingTransport binding. This should be tested, because I'm not 100% sure it supports the partitioning feature. However all necessary features are working because we are using this setup at a current integration
project.
Also be sure to check Paolo's blog for all the necessary information regarding configuration and setup: http://code.msdn.microsoft.com/windowsazure/How-to-integrate-BizTalk-f0195690
Glenn Colpaert - Microsoft Integration MVP - Blog : http://blog.codit.eu

IMAC seems not compatible with Road Runner. Can send, not reply or send

Started having problems with RR on IMAC/Leopard. RR says it is a MAC problem. Can receive but not reply or send, so I have to go to webmail, wasting time. Is it better to use Mac Mail? Would that solve the problem?

This is a known issue with road runner e-mail and the mac mail app. Seeing as the mac mail app works just fine with any other e-mail provider, logically the issue is with road runner's e-mail service.
In my experience, Road Runner is severely lacking in Mac support. When I used to use them (I recently switched to FiOS), any time I would call support due to an outage, I was always told that "our internet doesn't work with macs" or "the problem is that you have a mac. You need to call Apple for support."
At any rate, if you want to use mac mail, I would suggest getting a new e-mail provider, such as Gmail.

In iPlanet Web Proxy Server 3.6 on Win2000, how do I turn on authentication? I want to force users to enter an id and pw when they go thru the proxy to websites out on the net. Thanks

Mal,
You'll need to point to some user database, either the local db on Proxy or an ldap server. The ldap server is the best choice as the local db just stores users in a flat file and becomes unreliable after 1000 entries.
To enable authentication, manage the proxy server instance and navigate to Restrict Access.
From there, turn on access control, and click on the Permissions button. This will open up a new window to allow you to setup your access control rules and restrictions. When you're done, click on Done, apply your changes and restart the proxy server and you should be on your way.

IE 6.0 seems not compatible with iplanet web proxy server 3.6

Similar Messages

Maybe you are looking for