WSO2 Publisher/Store api-manager.xml config GatewayEndpoint with gateway clustering -


if have multiple gateway worker nodes, how can config gatewayendpoint?

i read post of setup gateway endpoint, case has 1 gateway worker node. had nginx node before wso2 clustering, need display final endpoint url in store end users. serverurl, can config url: "https://mgt.gw.devzone.com/services/" .

<apigateway>    <environments>        <environment type="hybrid" api-console="true">             <name>production , sandbox</name>             <description>this hybrid gateway handles both production , sandbox token traffic.</description>                       <serverurl>https://<api-gateway-host>:9443/services/</serverurl>             <username>${admin.username}</username>             <password>${admin.password}</password>                       <gatewayendpoint>http://<api-gateway-host>:8280,https://<api-gateway-host>:8243</gatewayendpoint>        </environment>    </environments> </apigateway>

yes serverurl should point gw manager node. when specifying gw worker urls need point nginx. gatewayendpoint including here should resolve nginx , nginx loadbalance request between worker nodes. url add here shown in api store.


-

Comments

Post a Comment

Popular posts from this blog

loops - Spock: How to use test data with @Stepwise -

i used @stepwise automation. 8 test methods running sequentially complete process. 1 of methods take parameter , want pass different parameters method. but problem is: method takes first set of parameter, parameters processed and instead of proceeding next method, method takes next set of parameter. the source looks like: @stepwise class aosearchpagetest extends gebreportingspec { def "first_method"() { } def "second_method"() { when: @ particularpage then: process(area) process(coutntry) process(airport) process(dest_area) process(dest_coutntry) process(dest_airport) where: area << ["asia","europe"] country << ["japan","uk"] port << ["narita","london"] dest_area << ["asia","europe"] dest_country << ["k...
Read more

amazon web services - S3 Pre-signed POST validate file type? -

i know it's possible put limit on file size content-length-range header. possible validate file type? https://docs.aws.amazon.com/amazons3/latest/dev/httppostforms.html#policyconditions i see there content-type header, if set say, audio/mp3 allow mp3 files , return error if file not mp3? i found previous question answers mention validating file size: s3 direct upload restricting file size , type you can specify content-type @ post request. you can specify @ signature, post must done content-type: { "expiration": "2007-12-01t12:00:00.000z", "conditions": [ {"acl": "public-read" }, {"bucket": "johnsmith" }, {"content-type: "audio/mp3"} ] } creating html form (using aws signature version 4) edit: @ previous question found, checking content-type.
Read more