Following are the request headers
1. Request URL:
https://cloudmgt.cloudpreview.wso2.com/cloudmgt/site/pages/index.jag
2. Request Method:
GET
3. Status Code:
200 OK
4. Request Headersview source
1. Accept:
Hi,
There is an issue reported for this in different scenario [1]
[1]https://issues.apache.org/jira/browse/CASSANDRA-6536
Thanks
Shammi
On Fri, Feb 28, 2014 at 11:50 AM, Nuwan Silva nuw...@wso2.com wrote:
Hi All,
When running a high load on a MB Cluster we have observed Cassandra
Hmm.. That's strange. You see HTTP Headers in the downloaded file itself?
On Fri, Feb 28, 2014 at 1:43 PM, Amila Maha Arachchi ami...@wso2.comwrote:
Following are the request headers
1. Request URL:
https://cloudmgt.cloudpreview.wso2.com/cloudmgt/site/pages/index.jag
2. Request
I am re-posting the request headers with clarity.
Isuru, yes, response headers were seen inside the downloaded file.
Request URL:
https://cloudmgt.cloudpreview.wso2.com/cloudmgt/site/pages/index.jag
Request Method: GET
Status Code:200 OK
Request Headersview source
Hi,
Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal
4.2.0.
Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with
AS5.3.0
Here I have created branch[1] upon on $subject.(Regard 4.3.0 shift commits
will add to here[1], late we will merge it to master and
%s/kernal/kernel
On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Jaggery-0.9.0.ALPHA4.wso2v3 was recently released and it is on kernal
4.2.0.
Therefore we have to update jaggery to kernal 4.3.0 to ship jaggery with
AS5.3.0
Here I have created branch[1] upon
Hi Amila,
If the response contains the Content-Type as text/html, then it would
displayed in the browser itself. But that's not the issue in your case.
It seems the response you are seeing is GZip encoded since the
Content-Encoding header is set to GZip. It's hard to understand why Chrome
Hi Kasun,
I think the problem here is that the HTTP headers were also part of the
response body. So, the Chrome does not have any idea about the Content-Type.
On Fri, Feb 28, 2014 at 2:42 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Amila,
If the response contains the Content-Type as
Refereed link
[1] https://github.com/wso2/jaggery/tree/branch-for-kernel4.3.0
On Fri, Feb 28, 2014 at 2:42 PM, Isuru Perera isu...@wso2.com wrote:
%s/kernal/kernel
On Fri, Feb 28, 2014 at 2:39 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Jaggery-0.9.0.ALPHA4.wso2v3 was recently
thanks maninda
Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300
On Fri, Feb 28, 2014 at 2:36 PM, Maninda Edirisooriya mani...@wso2.com wrote:
Hi Shavantha,
If you want comma
Congratulations Malintha
On Thu, Feb 27, 2014 at 9:53 AM, Harsha Thirimanna hars...@wso2.com wrote:
Congratulations...
On Feb 27, 2014 9:51 AM, Shazni Nazeer sha...@wso2.com wrote:
Congratulations Malintha!!
Shazni Nazeer
Senior Software Engineer
Mob : +94 715 440 607
LinkedIn :
Thanks all. Created the tables manually.
On Fri, Feb 28, 2014 at 11:08 AM, Lasantha Fernando lasan...@wso2.comwrote:
Hi,
There is a spelling mistake in the Postgresql db script. You can use the
attached one.
Thanks,
Lasantha
On 27 February 2014 21:08, Ragavan Thiruchittampalam
Observed this behaviour when enabled wire logs.
TID: [0] [ELB] [2014-02-28 03:58:10,445] DEBUG
{org.apache.synapse.transport.http.wire} - HTTP/1.1 200 OK[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [ELB] [2014-02-28 03:58:10,445] DEBUG
{org.apache.synapse.transport.http.wire} -
---
Developer Studio Eclipse-Tools #1451 was successful.
---
This was manually triggered by Maheshika Goonetilleke.
Hi,
As I have seen synapse-samples_*.jar is not the actual jar which need to
be in class path, even I delete the above jar I can run the sample.
Correct jar would be org.wso2.esb.samples_4.8.1.jar
more proof
[image: Inline image 1]
On Fri, Feb 28, 2014 at 9:07 AM, Rukshani Weerasinha
Hi,
Please find $Subject in [1]
[1]http://builder1.us1.wso2.org/~apim/28-02-2014/wso2am-2.0.0.zip
Thanks,
Lakmali
--
Lakmali Baminiwatta
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile: +94 71 2335936
blog : lakmali.com
Hi All,
If we take a released chunk as an example chunk 7 [1], under
turing-chunk07/product-releases/ again we get chunk (01-08). Is there any
special reason to put chunk 08 also without putting only chunk (01-07).
[1] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk07
--
Hi Gayan,
As you know when we release a chunk we get a snapshot of the current branch
at the moment and move it to tag directory, The possible ways are having
chunk 08 under the chunk 07 tag is, someone has created chunk 08 before we
release chunk 7 , or there are two active chunks at the
Hi Sudarshana,
On Thu, Feb 27, 2014 at 11:53 PM, Sudarshana Gurusinghe
sgurusin...@gmail.com wrote:
Hi,
I thought of contributing to your ESB.
Nice :)
Following the instructions on your site (
https://docs.wso2.org/display/ESB481/Building+from+Source) I have issued
the command to do
Do we need to mention this file at all? It seems like the sample JARs are
installed in the correct places during installation and that the samples
run fine without needing to verify anything. If there's nothing for the
user to do, we shouldn't mention it. Gayan, can you please confirm?
Thanks,
Hi API-M team,
I have encounter $subject in my local machine as well as server several
times. The following logs from the server which we supposed to deploy the
WSO2 Con API. When this happens press Ctrl+C and quite the starting and
after again start the server then it'll starting.
Hi,
I think esb team can take that decision. Possible solutions would be we
shouldn't mention it (as you proposed) or we should mention the correct JAR
name.
If someone need to change the sample bit and explore things then mentioning
correct JAR name is much helpful rather black boxing the JAR
When the page loads successfully, then also content is gzip encoded. So,
that can't be the reason.
On Fri, Feb 28, 2014 at 2:42 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Amila,
If the response contains the Content-Type as text/html, then it would
displayed in the browser itself. But
On Thu, Feb 27, 2014 at 3:27 PM, Gayan Gunawardana ga...@wso2.com wrote:
Thanks Malaka, btw seems like that synapse-samples_2.1.2.wso2v4.jar was
patched, same bundle can be seen inside patch. so we are loading from
there right?
FYI
That doesn't necessarily means that the bundle is
24 matches
Mail list logo
