[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [corona-dev] Problems with Proxies
|
I don't exactly undestand what do you mean by saying "mapping URL".
There is already a bug for proxy:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=164301 .
In fact the problem is wide. First of all all HTTP traffic can go
through HTTP proxy. This is OK with our PC which is access through HTTP.
But then, ECF natively goes by its own protocol. I'm not sure if shared
object can go with HTTP. If not, then some restrictive networks won't
let it through. If HTTP proxy supports connect operation (used for
https) then it could be used for ECF as well. Going further one might
have HTTP proxy for HTTP and SOCKS proxy for other traffic. Then we
would need double proxy - one for PC web services and second for WS.
Good thing is that ECF also thinks of this. Unfortunately they still
have this issue in NEW status and no target milestone defined.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=119933
Marcin
O'Flynn, Dennis napisał(a):
I was able to get Corona’s 1.0.0M5 release installed on Corona’s
virtual server and access it from a Corona enabled workbench. However,
all of this was from my home where a I could access the remote server
directly.
Unfortunately, problems with using a proxy server were encountered
once I tried this from work . The Workbench client is behind a
firewall / proxy. Consequently all of the Repository Descriptors that
reference a URL need to be mapped to the appropriate proxy address.
This poses an interesting problem. Each team member may have his/her
own set of proxy address to use. Thus the mapping of the Repository
Descriptor’s URL is a function of the PCC and Team Member.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
------------------------------------------------------------------------
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
